Date: Tue, 8 Jun 2004 10:20:47 +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: <200406081020.48658.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=_gbXxAP+lmgcInci 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: > To get around this, we can use -pthread to link shared objects as well > as executables.=20 And there is another thing: I seem to remember that the getting rid of=20 =2Dpthread (I remember at one time -pthread was completely gone from gcc in= =20 =2DCURRENT, why this was reversed I don't know) was meant to facilitate usi= ng=20 one of the three threads-libraries now available in -CURRENT: libc_r,=20 libpthread (formerly libkse) and libthr. How is this supposed to be possibl= e=20 with -pthread? And if -pthread will always link to libpthread, won't the=20 problem then still be the same if someone chooses to set PTHREAD_LIBS to=20 =2Dlthr/-lc_r? =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=_gbXxAP+lmgcInci Content-Type: application/pgp-signature Content-Description: signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQBAxXbgXhc68WspdLARAuwrAKCDQ83tmnMP7RX8lIqhZY5dVmLxRQCfTU+R TlFYirXwUBAtYNrXZjBCIG4= =WjY1 -----END PGP SIGNATURE----- --Boundary-02=_gbXxAP+lmgcInci--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200406081020.48658.michaelnottebrock>