Date: Tue, 10 Feb 2004 17:23:14 -0800 From: Kris Kennaway <kris@obsecurity.org> To: Marco van de Voort <marcov@stack.nl> Cc: freebsd-ports@freebsd.org Subject: Re: How to determine which pthread, was: Re: last libc_r dependenciesleft on current Message-ID: <20040211012314.GA44192@xor.obsecurity.org> In-Reply-To: <20040210223625.C6F4C83@toad.stack.nl> References: <20040210223625.C6F4C83@toad.stack.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
--+QahgC5+KEYLbs62 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Feb 10, 2004 at 11:36:25PM +0100, Marco van de Voort wrote: >=20 > (Oops, sorry Fritz, now to the list :-) >=20 > > after removing libc_r.so and rebuilding my ports (gettext port upgrade) > > there here are three ports left with "hardcoded" libc_r dependency and > > therefore failed to build: > >=20 > > x11-toolkits/qt32, lang/gcc34 (not so important) and java/jdk13 >=20 > Btw, >=20 > lang/fpc-devel (and to a lesser degree lang/fpc) are not libc_r dependant > themselves, but generate libc_r programs when language threading is used. >=20 > I'll fix this in the coming weeks, but rather like to do this runtime.=20 >=20 > How can I detect (in a non C/libc program, iow without using headers or > libraries, so in the general FreeBSD environment), whether I should pass > -lc_r to the linker or -lc -lpthread ?=20 > (sysctl or uname based solutions come to mind) Look at how bsd.port.mk decides. Kris --+QahgC5+KEYLbs62 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAKYQCWry0BWjoQKURAsZzAJkByUMlM0rR717cllXFMCZ+wUzMbwCfSYCH 4N2IbqIlkuUAnkqwsTVdmnI= =SJCb -----END PGP SIGNATURE----- --+QahgC5+KEYLbs62--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040211012314.GA44192>