From owner-freebsd-gnome@FreeBSD.ORG Tue Jun 8 07:27:10 2004 Return-Path: Delivered-To: freebsd-gnome@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1889116A4CE; Tue, 8 Jun 2004 07:27:10 +0000 (GMT) Received: from ylpvm43.prodigy.net (ylpvm43-ext.prodigy.net [207.115.57.74]) by mx1.FreeBSD.org (Postfix) with ESMTP id C4C2143D45; Tue, 8 Jun 2004 07:27:09 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (adsl-63-207-60-35.dsl.lsan03.pacbell.net [63.207.60.35])i587R7qE022779; Tue, 8 Jun 2004 03:27:07 -0400 Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id D6D5651955; Tue, 8 Jun 2004 00:27:06 -0700 (PDT) Date: Tue, 8 Jun 2004 00:27:06 -0700 From: Kris Kennaway To: Dan Nelson Message-ID: <20040608072706.GA82243@xor.obsecurity.org> References: <1086663455.1258.79.camel@server.mcneil.com> <20040608044844.GA89198@dan.emsphone.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="6c2NcOVqGQ03X4Wi" Content-Disposition: inline In-Reply-To: <20040608044844.GA89198@dan.emsphone.com> User-Agent: Mutt/1.4.2.1i cc: freebsd-amd64@freebsd.org cc: freebsd-gnome@freebsd.org cc: freebsd-threads@freebsd.org cc: freebsd-current@freebsd.org cc: Daniel Eischen cc: Sean McNeil Subject: Re: weak implementation of threads has problems - kse fix attached X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: GNOME for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Jun 2004 07:27:10 -0000 --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--