security/nmap & gcc3.3?
Oliver Eikemeier
eikemeier at fillmore-labs.com
Wed Jan 28 17:43:02 PST 2004
Charles Swiger wrote:
> Hi, all--
>
> On a FreeBSD-4.9 system, nmap-3.50 builds fine using the stock cc (gcc
> version 2.95.4 20020320), but fails using gcc33 (version 3.3.3 20040126):
>
> [...]
>
> I would gather that nmap is setting the linking path in a fashion which
> causes the gcc33 version of libstdc++ to not be found, or to not be
> linked in by default?
>
> Retrying the linking stage by hand as follows produces a working binary:
>
> 58-sec# /usr/local/bin/g++33
> -L/usr/local/lib/gcc-lib/i386-portbld-freebsd4.9/3.3.3/
> -L/usr/local/lib -rpath=/usr/lib:/usr/local/lib -L/usr/lib -Lnbase
> -Lnsock/src/ -o nmap main.o nmap.o targets.o tcpip.o nmap_error.o
> utils.o idle_scan.o osscan.o output.o scan_engine.o timing.o charpool.o
> services.o protocols.o nmap_rpc.o portlist.o NmapOps.o TargetGroup.o
> Target.o FingerPrintResults.o service_scan.o NmapOutputTable.o -lm
> -lssl -lcrypto -lnbase -lnsock -lpcre -lpcap -lstdc++
>
> [ Other ports I've tried which use g++33 link fine; this problem seems
> specific to security/nmap... ]
I try to look into this over the weekend, or do you have a patch?
-Oliver
More information about the freebsd-ports
mailing list