Date: Wed, 24 Sep 2003 12:15:10 -0400 (EDT) From: Daniel Eischen <eischen@vigrid.com> To: Ian Dowse <iedowse@maths.tcd.ie> Cc: Freebsd Current <current@freebsd.org> Subject: Re: Fixing -pthreads (Re: ports and -current) Message-ID: <Pine.GSO.4.10.10309241213230.16585-100000@pcnet5.pcnet.com> In-Reply-To: <200309241703.aa94887@salmon.maths.tcd.ie>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 24 Sep 2003, Ian Dowse wrote: > 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. > > 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. Hey, neat. I wouldn't have known how to do such a thing from gcc. -- Dan Eischen
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.10.10309241213230.16585-100000>