Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 29 Jan 2004 16:17:11 +0100
From:      Simon Barner <barner@in.tum.de>
To:        Charles Swiger <cswiger@mac.com>
Cc:        ports@freebsd.org
Subject:   Re: security/nmap & gcc3.3?
Message-ID:  <20040129151711.GA1416@zi025.glhnet.mhn.de>
In-Reply-To: <1E5E3622-51D2-11D8-96D6-003065A20588@mac.com>
References:  <1E5E3622-51D2-11D8-96D6-003065A20588@mac.com>

next in thread | previous in thread | raw e-mail | index | archive | help

--r5Pyd7+fXNt84Ff3
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Charles Swiger wrote:

[...]

> I would gather that nmap is setting the linking path in a fashion which=
=20
> causes the gcc33 version of libstdc++ to not be found, or to not be=20
> linked in by default?

Yes, that's the problem.
=20
> Retrying the linking stage by hand as follows produces a working binary:
>=20
> 58-sec# /usr/local/bin/g++33 =20
> -L/usr/local/lib/gcc-lib/i386-portbld-freebsd4.9/3.3.3/=20
> -L/usr/local/lib  -rpath=3D/usr/lib:/usr/local/lib -L/usr/lib -Lnbase=20
> -Lnsock/src/  -o nmap main.o nmap.o targets.o tcpip.o nmap_error.o=20
> utils.o idle_scan.o osscan.o output.o scan_engine.o timing.o charpool.o=
=20
> services.o protocols.o nmap_rpc.o portlist.o NmapOps.o TargetGroup.o=20
> Target.o FingerPrintResults.o service_scan.o NmapOutputTable.o -lm =20
> -lssl -lcrypto -lnbase -lnsock -lpcre -lpcap -lstdc++
>=20
> [ Other ports I've tried which use g++33 link fine; this problem seems=20
> specific to security/nmap... ]

This is very strange. g++ is supposed to link against lstdc++ without
any additional options.

I tried to compile nmap with my older version of g++33, and it compiled
and linked just fine:

g++33 -v
Reading specs from /usr/local/lib/gcc-lib/i386-portbld-freebsd4.9/3.3.3/spe=
cs
Configured with: ./..//gcc-3.3-20031208/configure --disable-nls
--with-gxx-include-dir=3D/usr/local/lib/gcc-lib/i386-portbld-freebsd4.9/3.3=
=2E3/
include/c++/ --with-system-zlib --enable-shared --enable-threads
--enable-threads=3Dposix --prefix=3D/usr/local i386-portbld-freebsd4.9

Thread model: posix
gcc version 3.3.3 20031208 (prerelease) [FreeBSD]

I'd suggest that you make sure that you have the very latest version of
the gcc33 port installed, and if the problem continues to exist, IMO you
should contact the gcc maintainer (gerald@).

Simon

--r5Pyd7+fXNt84Ff3
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (FreeBSD)

iD8DBQFAGSP3Ckn+/eutqCoRAh4LAJ46Qzem9CQe5CvHIn3suTsZv9uO9wCg24fF
ahGoqY2CwViG2xQWO/IHMLI=
=0Yck
-----END PGP SIGNATURE-----

--r5Pyd7+fXNt84Ff3--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040129151711.GA1416>