Re: threads stuff/UnixWare

On Wed, 12 May 2004, Larry Rosenman wrote:

>
>
> --On Wednesday, May 12, 2004 15:02:30 -0300 "Marc G. Fournier"
> <scrappy@postgresql.org> wrote:
>
> > On Wed, 12 May 2004, Larry Rosenman wrote:
> >
> >>
> >>
> >> --On Wednesday, May 12, 2004 14:14:30 -0300 "Marc G. Fournier"
> >> <scrappy@postgresql.org> wrote:
> >>
> >> > On Wed, 12 May 2004, Larry Rosenman wrote:
> >> >
> >> >> I'd LIKE to be able to have PG wrappers for those functions, and have
> >> >> the first invocation of them look via dlsym() for the real ones, and
> >> >> if they are NOT there, use fake functions that assume we are NOT
> >> >> threaded.
> >> >
> >> > Wouldn't it be easier to have a #define?
> >> >
> >> > Correct me if I'm wrong here, but the problem is that we are expecting
> >> > thread functinos to be called x_, while Unixware defines them as
> >> > pthread_, right? so make Unixware specific #defines that map x_ to
> >> > pthread_ ...
> >> No, we are expecting them to have pthread_*.
> >>
> >> On UnixWare, to get the pthread_* functions, you need to invoke a
> >> compiler option (-Kpthread), to cause libpthread to be linked in.
> >>
> >> Since libpq.so now REQUIRES the function, we need to either:
> >>
> >> 1) force ANY program that uses libpq to be compiled/linked with -Kpthread
> >
> > Ummm, shouldn't that be added to the port specific Makefile?
> See my reply to Tom.  It forces ALL libpq using programs to be
> linked with -Kpthread, which was deemed unacceptable.

deemed unacceptable by whom?  Sounds to me alot simpler of a solution then
making wrappers for the pthread_* functions just to accommodate one OS ...
I could see it if this was a wide-spread problem, but it doesn't appear to
be ...

----
Marc G. Fournier           Hub.Org Networking Services (http://www.hub.org)
Email: scrappy@hub.org           Yahoo!: yscrappy              ICQ: 7615664