cvs commit: src/lib/libpthreadMakefilesrc/lib/libpthread/thread thr_attr_get_np.c thr_attr_init.c thr_attr_setcreatesuspend_np.c

[Daniel Eischen]

On Fri, 18 Apr 2003, Wesley Morgan wrote:

> On Fri, 18 Apr 2003, Daniel Eischen wrote:
> 
> > >   This library now passes all of the ACE tests that libc_r passes
> > >   with the exception of one.  It also seems to work OK with KDE
> > >   including konqueror, kwrite, etc.  I haven't been able to get
> > >   mozilla to run due to lack of java plugin, so I'd be interested
> > >   to see how it works with that.
> >
> > Thanks to marcel, I've finally figured out how to get mozilla
> > running.  It seems to work OK with these changes, but having
> > never used it before, I'm not sure what to expect.
> 
> Ok, I'm a but confuzzled by all these threading libraries. Now we have
> libc_r, libthr, and libpthread? How can I alter the behavior of "-pthread"
> to use a different library? As far as I can tell, only libc_r is actually

-pthread is a FreeBSD-specific hack that was needed when we
could not link to both libc and libc_r.  5.0-current has not
needed it for a couple of years.  Folks should probably be
encouraged to just use -lc_r, -lthr, or -lkse (will become
-lpthread again shortly).

> linked in with a buildworld, so when is it planned to make these
> available? What are the advantages and disadvantages? Which library is
> more complete? Can someone do a summary of some sort to help out the
> consumers?

You have to manually build and install libthr and libpthread.
I'll hook libpthread in to the world as soon as we fix some
other problems.

libc_r is probably more complete, but libthr and libpthread
probably aren't that far from the mark.  Performance should
be better with the latter two.

-- 
Dan Eischen