Re: threads stuff/UnixWare

From: Larry Rosenman <ler(at)lerctr(dot)org>
To: "Marc G(dot) Fournier" <scrappy(at)postgresql(dot)org>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: threads stuff/UnixWare
Date: 2004-05-12 18:05:15
Message-ID: 1D2847835C3B28B5B1609047@lerlaptop.lerctr.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

--On Wednesday, May 12, 2004 15:02:30 -0300 "Marc G. Fournier"
<scrappy(at)postgresql(dot)org> wrote:

> On Wed, 12 May 2004, Larry Rosenman wrote:
>
>>
>>
>> --On Wednesday, May 12, 2004 14:14:30 -0300 "Marc G. Fournier"
>> <scrappy(at)postgresql(dot)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.

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

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message pgsql 2004-05-12 18:10:52 Configuration patch
Previous Message Bruno Wolff III 2004-05-12 18:05:06 Re: Probably security hole in postgresql-7.4.1