From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Larry Rosenman <ler(at)lerctr(dot)org>, Zeugswetter Andreas SB SD <ZeugswetterA(at)spardat(dot)at>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: threads stuff/UnixWare |
Date: | 2004-05-13 15:07:21 |
Message-ID: | 200405131507.i4DF7L724903@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > Larry Rosenman wrote:
> >> I agree. the only issue is how to set up our makefiles to only do the
> >> -Kpthread/-pthreads(gcc) flags on the client code, and not do it for
> >> the backend itself.
>
> > I think mixing a pgport that has thread flags with a backend that does
> > not is more risky than just compiling everything with the same thread
> > flags.
>
> Can we get this straight: is -Kpthread a compile flag or just a link flag?
> If the latter then it should not be needed in building the libpgport files.
> If the former then adding it to LDFLAGS is the wrong thing.
-Kpthread is needed for both compile and link, and the PTHREAD_CFLAGS is
used for both compile and link phases.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
From | Date | Subject | |
---|---|---|---|
Next Message | Oleg Bartunov | 2004-05-13 15:13:54 | Re: Subtle pg_dump problem... |
Previous Message | Tom Lane | 2004-05-13 14:35:09 | Re: threads stuff/UnixWare |