Re: thread_test.c problems

From: <wespvp(at)syntegra(dot)com>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: PostgreSQL-general <pgsql-general(at)postgresql(dot)org>, joseph speigle <joe(dot)speigle(at)jklh(dot)us>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: thread_test.c problems
Date: 2004-04-26 05:25:36
Message-ID: BCB20780.7E6D%wespvp@syntegra.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

On 4/25/04 11:06 PM, "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us> wrote:

> OK, CVS is ready. I unconditionally defined:
>
> -D_REENTRANT -D_THREAD_SAFE -D_POSIX_PTHREAD_SEMANTICS
>
> for all ports. It can't hurt if they are not supported, but it makes
> our job easier for porting. It allowed me to remove almost all the
> port-specific thread stuff. The other tests are done by configure and
> thread_test.
>
> Should fix Darwin compile and other platforms without mucking with the
> thread detection code.

Ok, I'll do another build and send you the output.

Wes

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Bruno Baguette 2004-04-26 09:21:19 Restart increment to 0 each year = re-invent the sequences mecanism ?
Previous Message Bruce Momjian 2004-04-26 04:06:04 Re: thread_test.c problems

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2004-04-26 06:34:58 Re: Bringing PostgreSQL torwards the standard regarding
Previous Message Dennis Bjorklund 2004-04-26 05:15:08 Re: Bringing PostgreSQL torwards the standard regarding