Date: Tue, 8 Jun 2004 00:27:06 -0700 From: Kris Kennaway <kris@obsecurity.org> To: Dan Nelson <dnelson@allantgroup.com> Cc: Sean McNeil <sean@mcneil.com> Subject: Re: weak implementation of threads has problems - kse fix attached Message-ID: <20040608072706.GA82243@xor.obsecurity.org> In-Reply-To: <20040608044844.GA89198@dan.emsphone.com> References: <1086663455.1258.79.camel@server.mcneil.com> <Pine.GSO.4.10.10406080028070.11500-100000@pcnet5.pcnet.com> <20040608044844.GA89198@dan.emsphone.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--6c2NcOVqGQ03X4Wi Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jun 07, 2004 at 11:48:45PM -0500, Dan Nelson wrote: > In the last episode (Jun 08), Daniel Eischen said: > > No, I don't want to litter all our thread libraries with strong > > references. As I've said before, build your shared libraries > > correctly so they don't bring in the threads library. >=20 > A good addition to bsd.port.mk, right next to the "possible network > server" etc checks, might be to run ldd on all installed shared > libraries and print a warning if any threads libraries show up. There > are a huge number of ports that install shlibs linked to libpthreads. Some of these are probably correct, in that the library started using libpthreads internally and there are a large number of clients that would otherwise need to be changed to link to that library. Kris --6c2NcOVqGQ03X4Wi Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAxWpKWry0BWjoQKURAn+6AJ46khXPmJulpz485nM4Xb2p43vargCdFEma OpAqGmYFBmYWVAdxb7FFKgk= =yXEK -----END PGP SIGNATURE----- --6c2NcOVqGQ03X4Wi--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040608072706.GA82243>