Each thread library has it's own API, so you should be careful about which
one you choose.  Check the code for the server and try to find out what
thread library it uses.  If you just want to try the "kick the tires, light
the fires" approach just compile the server and see if you get errors.  If
you get link errors chances are, you have the wrong thread library.

Also, look in the Makefile for the linker settings, and you should see
something like "-lthread_library" as a C compiler option, where
thread_library is the name of the thread library. 

Hope that helps.



Richard Schilling
Web Integration Programmer/Webmaster
phone: 360.856.7129
fax: 360.856.7166
URL: http://www.affiliatedhealth.org

Affiliated Health Services
Information Systems
1971 Highway 20
Mount Vernon, WA USA


> -----Original Message-----
> From: Ian Harding [mailto:iharding@pakrat.com]
> Sent: Wednesday, April 25, 2001 7:34 AM
> To: port-vax@netbsd.org
> Subject: Thread Library - A Little Off Topic
> 
> 
> This is a little off topic since it concerns the i386 port, but here
> goes anyway...
> 
> I have a rare opportunity at work to set up a web/database 
> server for an
> application I developed using whatever operating system I choose.  Of
> course, I chose NetBSD.  The problem is that the web server
> (AOLServer) is not 'confirmed' to run on NetBSD.  It will 
> build on Open
> and FreeBSDs.  The reason AOL gives me is that NetBSD does not have a
> 'thread library.'  I since found a couple of thread libraries in the
> packages collection and installed one (PTL).
> 
> My question is, should this be sufficient to build a program that
> requires a thread library (whatever that is.)?  I tried to build
> AOLServer by telling the Makefile it was compiling on OpenBSD.  The
> makefile has sections for both OpenBSD and FreeBSD.  Me looking at a
> makefile is a bit like a pig looking at a wristwatch.
> 
> Second question, how big of an ordeal is this likely to be?  Should
> I give up?
> 
> Ian
>