Re: threads stuff/UnixWare - Mailing list pgsql-hackers

From Larry Rosenman
Subject Re: threads stuff/UnixWare
Date
Msg-id 8DA82BC6196820A4BDFF5EB8@lerlaptop.lerctr.org
Whole thread Raw
In response to Re: threads stuff/UnixWare  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: threads stuff/UnixWare  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers

--On Wednesday, May 12, 2004 13:18:35 -0400 Tom Lane <tgl@sss.pgh.pa.us> 
wrote:

> Larry Rosenman <ler@lerctr.org> writes:
>> --On Wednesday, May 12, 2004 12:58:58 -0400 Tom Lane <tgl@sss.pgh.pa.us>
>>> In what way does the current thread stuff not work for you?
>
>> In the initdb compile:
>
>> Undefined                       first referenced
>> symbol                              in file
>> pthread_mutex_unlock                libpq.so
>> pthread_getspecific                 libpq.so
>> pthread_mutex_lock                  libpq.so
>> pthread_key_create                  libpq.so
>> pthread_once                        libpq.so
>> pthread_setspecific                 libpq.so
>
> Hmm.  And that means what?  Does Unixware not have these functions?
> Are we just failing to suck in the needed library?
>
>             regards, tom lane
No, we don't pass the -Kpthread (thread CFLAGS) to the C links.

This is the whole discussion we had back in January/February about forcing
-Kpthread for *ALL* libpq using programs, or dynamically determining
if the image already is linked -Kpthread, or not supporting threads
at all on UW.

#3 is unacceptable to me.

LER



-- 
Larry Rosenman                     http://www.lerctr.org/~ler
Phone: +1 972-414-9812                 E-Mail: ler@lerctr.org
US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: threads stuff/UnixWare
Next
From: Greg Stark
Date:
Subject: Re: Probably security hole in postgresql-7.4.1