Date: Tue, 8 Jun 2004 10:07:13 +0200 From: Michael Nottebrock <michaelnottebrock@gmx.net> To: freebsd-ports@freebsd.org Cc: Joe Marcus Clarke <marcus@freebsd.org> Subject: Re: RFC: [Long] Change PTHREAD_LIBS to -pthread for -CURRENT Message-ID: <200406081007.24315.michaelnottebrock@gmx.net> In-Reply-To: <1086673141.18374.35.camel@shumai.marcuscom.com> References: <1086673141.18374.35.camel@shumai.marcuscom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--Boundary-02=_8OXxAeUPHC/H7Ns Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Tuesday 08 June 2004 07:39, Joe Marcus Clarke wrote: > So, I propose changing PTHREAD_LIBS to -pthread for -CURRENT. This will > match what we have in 4.X, and will last for the life of 5.X going > forward. The threading people tell me this is doable now. Thoughts? My knowledge about both our rtld and our threads implementation is limited,= =20 however: I see that linking via -lpthread is what's done on Linux/glibc.=20 Linux/glibc is the reference and development platform of a huge majority of= =20 the software which exists in the ports-collection. Would it be possible to= =20 keep -lpthread as PTHREAD_LIBS and do whatever glibc does (if it does=20 anything at all) to prevent the breakage you describe from happening? =2D-=20 ,_, | Michael Nottebrock | lofi@freebsd.org (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org --Boundary-02=_8OXxAeUPHC/H7Ns Content-Type: application/pgp-signature Content-Description: signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQBAxXO8Xhc68WspdLARAl0PAJ0TGqZiZeWTVvkecH1kQ73B3nVM/gCbBPFn xR9rqO8jp9ZIkZ8kCEBGO/U= =wcMf -----END PGP SIGNATURE----- --Boundary-02=_8OXxAeUPHC/H7Ns--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200406081007.24315.michaelnottebrock>