weak implementation of threads has problems - kse fix attached
green at freebsd.org
Tue Jun 8 15:30:23 GMT 2004
On Tue, Jun 08, 2004 at 12:27:06AM -0700, Kris Kennaway wrote:
> 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.
> > 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.
In this case, Berkeley DB 4.2 actually doesn't even compile in
pthreads support (which it would use exclusively for mutexes);
since it compiles in "test-and-set" mutex support, the linking to
-lpthread is 100% bogus.
Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\
<> green at FreeBSD.org \ The Power to Serve! \
Opinions expressed are my own. \,,,,,,,,,,,,,,,,,,,,,,\
More information about the freebsd-threads