Comments about FreeBSD threading from Apache people

[Daniel Eischen]

On Thu, 13 Nov 2003, Craig Rodrigues wrote:

> On Thu, Nov 13, 2003 at 01:51:00AM -0500, Daniel Eischen wrote:
> > Supposedly, libkse will be default for archs in which
> > it is supported (currently i386, amd64, ia64) for
> > 5.2-RELEASE.  
> 
> What is the release criteria for this?  Is re@ going
> to make this decision?

Yes.

> > It is undecided whether it will be default
> > by means of installing an appropriate libmap.conf, or
> > by renaming libkse back to libpthread and changing
> > PTHREAD_LIBS to -lpthread (and also changing gcc -pthread
> > so that it links to libpthread instead of libc_r).
> 
> Hmm, this is indeed a tricky thing, and I don't know
> the best course of action to recommend.  Where is
> the best place to follow discussion related to this?

I dunno; ask re at .  It's their call.  I don't really
care one way or the other for 5.2-release, but for
5.3 libkse will going out as libthread.

> > Port maintainers shouldn't get too concerned about
> > this; they should continue to rely on PTHREAD_LIBS
> > and PTHREAD_CFLAGS.  I suppose there is the possibility
> > that some ports may want a specific threads library.
> > In that case, perhaps PTHREAD_LIBS can be overridden
> > by the port.  But you should probably ask ports@
> > to see if that is how it should be handled.
> 
> Well, for just maintaining a port, it is OK.
> However, for pushing changes back to the original
> package maintainers, you cannot really rely on
> PTHREAD_LIBS and PTHREAD_CFLAGS, because those
> variables are defined in /usr/ports/Mk/bsd.port.mk.

Don't use -lkse somewhere outside our ports tree; it
is just a temporary name.  In the future, whether it's
5.2 or 5.3, it will be libpthread.  Autoconf/configure/etc
scripts should first check for the presence of libpthread,
then libc_r.  Things that don't use autoconf et. al. can
always check the FreeBSD version (we'll bump it when
libkse becomes libpthread).

-- 
Dan Eischen