Date: Wed, 24 Sep 2003 13:24:10 -0400 From: Michael Edenfield <kutulu@kutulu.org> To: Ian Dowse <iedowse@maths.tcd.ie>, deischen@freebsd.org, Doug Barton <DougB@freebsd.org>, Freebsd Current <current@freebsd.org> Subject: Re: Fixing -pthreads (Re: ports and -current) Message-ID: <20030924172410.GB90989@wombat.localnet> In-Reply-To: <20030924171949.GA90989@wombat.localnet> References: <Pine.GSO.4.10.10309241029001.26896-100000@pcnet5.pcnet.com> <200309241703.aa94887@salmon.maths.tcd.ie> <20030924171949.GA90989@wombat.localnet>
next in thread | previous in thread | raw e-mail | index | archive | help
--gatW/ieO32f1wygP Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable * Michael Edenfield <kutulu@kutulu.org> [030924 13:21]: > * Ian Dowse <iedowse@maths.tcd.ie> [030924 12:03]: > > In message <Pine.GSO.4.10.10309241029001.26896-100000@pcnet5.pcnet.com>= , Daniel > > Eischen writes: > > >On Wed, 24 Sep 2003, Scott Long wrote: > > >> PTHREAD_LIBS is a great tool for the /usr/ports mechanism, but doesn= 't > > >> mean anything outside of that. > > > > > >That just meant it makes it easier to maintain ports so that > > >they are PTHREAD_LIBS compliant (they would break when linked). > > >I know it has no bearing on 3rd party stuff. > >=20 > > Just to throw one further approach out on the table, below is a > > patch that makes gcc read from a file to determine what library to > > associate with the -pthread flag. It's a hack of course, and probably > > neither correct or optimal. If you want to make -pthread mean libkse, > > create an /etc/pthread.libs that looks like: >=20 > I was looking through gcc last night to see how conceptually difficult > it would be to do something like this. But instead of a file, I was > thinking of this process: =20 I should point out that my main concern here is not technical but policy. Right now -pthread is implemented entirely as a gcc spec as part of LIB_SPEC. I didn't have time to get very far so I'm not sure how much special-case argument handling is done in gcc currently. Would this kind of approach, to moving the "-pthread" handling out of a specfile and into args handling code, fly with the FSF people? --Mike --gatW/ieO32f1wygP Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQE/cdM6CczNhKRsh48RAr/SAKDZYL2tfGRhGciICuiun7ffFbnxoQCaA1ZV KmaCd8iaoPpXCPG8raJvn2Q= =gFo6 -----END PGP SIGNATURE----- --gatW/ieO32f1wygP--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030924172410.GB90989>