New Ticket     Tickets     Wiki     Browse Source     Timeline     Roadmap     Ticket Reports     Search

Ticket #14429 (closed defect: worksforme)

Opened 6 years ago

Last modified 14 months ago

nessus-libraries build failed (libtool error)

Reported by: jon@… Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version: 1.6.0
Keywords: Cc:
Port: nessus-libraries libnasl

Description (last modified by ryandesign@…) (diff)

Nessus libraries fail to build, on macports 1.6.0 and a freshly installed & patched Leopard 10.5.2

cd libnessus && make
/bin/sh /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_net_nessus-libraries/work/nessus-libraries/libtool /usr/bin/gcc-4.0 -pipe -I../ -DHAVE_CONFIG_H  -DNESSUS_ON_SSL  -I. -DHAVE_SSL -I/opt/local/include -I/opt/local/include/openssl -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_net_nessus-libraries/work/nessus-libraries/include -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_net_nessus-libraries/work/nessus-libraries/libpcap-nessus   -g -c plugutils.c
libtool: warning: cannot infer operation mode from `/usr/bin/gcc-4.0'
libtool: you must specify a MODE
Try `libtool --help' for more information.
make[1]: *** [plugutils.o] Error 1
make: *** [all] Error 2

Warning: the following items did not execute (for nessus-libraries): org.macports.activate org.macports.build org.macports.destroot org.macports.install
Error: Status 1 encountered during processing.

Attachments

Portfile (1.4 KB) - added by jon@… 6 years ago.

Change History

comment:1 Changed 6 years ago by ryandesign@…

  • Cc opendarwin.org@… added

Cc'ing the port's maintainer.

This looks like it could be another variant of the "unable to infer tagged configuration" error we've seen with several ports since switching CC from "gcc" to "/usr/bin/gcc-4.0"

comment:2 Changed 6 years ago by jon@…

If I compile Nessus libraries from outside of Macports (i.e unpack tarball, ./comfigure, make) it works fine.

The difference seems to be on the name of the compiler that is used, i.e "gcc" (works) or "/usr/bin/gcc-4.0" (doesnt work)

Setting "configure.cc" to "gcc" in the Portfile seems to work. I'm not sure if this fits with the prevailing policy, but it does fix the build

Changed 6 years ago by jon@…

comment:3 Changed 6 years ago by jon@…

Same bug (and same fix) apply to "nessus-core" and "libnasl" ports.

Nessus-plugins seems unaffected.

comment:4 Changed 6 years ago by marktrolley@…

Thanks for the pointer on how to fix this. Any word on when it will make it into the ports tree?

comment:5 Changed 6 years ago by jon@…

No idea. I don't have commit access, and I don't know if my change fits with policy. There has been no comment in 2 months from the maintainer, so don't get your hopes up :-(

comment:6 Changed 6 years ago by ricci@…

  • Owner changed from macports-tickets@… to ricci@…
  • Status changed from new to assigned

comment:7 Changed 5 years ago by jmr@…

  • Port set to nessus-libraries

comment:8 Changed 5 years ago by chitopunk@…

Changing mode=link in macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_net_nessus-libraries/work/nessus-libraries/libtool fixed this problem

comment:9 Changed 5 years ago by anonymous

  • Milestone Port Bugs deleted

Milestone Port Bugs deleted

comment:10 Changed 4 years ago by ryandesign@…

  • Description modified (diff)

comment:11 Changed 2 years ago by jmr@…

  • Cc opendarwin.org@… removed
  • Status changed from assigned to new
  • Keywords nessus removed
  • Port changed from nessus-libraries to nessus-libraries libnasl
  • Owner changed from ricci@… to macports-tickets@…

-> nomaintainer

comment:12 Changed 2 years ago by jon@…

I've just built @2.2.6_1 on Lion, and all seems good now. This ticket can be closed.

comment:13 Changed 23 months ago by macsforever2000@…

  • Status changed from new to closed
  • Resolution set to worksforme

comment:14 Changed 14 months ago by ryandesign@…

The problem remains, as reported again in #38114.

Note: See TracTickets for help on using tickets.