From: | Wes <wespvp(at)syntegra(dot)com> |
---|---|
To: | Louis Gonzales <louis(dot)gonzales(at)linuxlouis(dot)net> |
Cc: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Build failures on RedHat 3.0 with openssl/kerberos |
Date: | 2006-03-14 21:53:02 |
Message-ID: | C03C975E.20B46%wespvp@syntegra.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 3/14/06 2:55 PM, "Louis Gonzales" <louis(dot)gonzales(at)linuxlouis(dot)net> wrote:
> Did you try to ./configure w/out "--enable-thread-safety?" I recently
> compiled postgreSQL 8.0.1 on Solaris and _needed_ --enable-thread-safety
> strictly for building Slony-I against postgresql with that feature enabled.
>
> What is the reason you are compiling this _with_ the feature?
> If it's necessary, then you may need to --with-includes= and/or --with-libs=
> with additional include directories, such as /usr/include:/usr/include/sys
> where-ever the thread .h files are for your OS.
>
> This configure attempt could be failing, because it can't locate the
> correct thread headers and/or libraries
Why would I not want to specify enable-thread-safety? I want to be able to
write threaded programs.
--enable-thread-safety works fine until I enable --with-krb5, so it is
finding the thread libraries.
Wes
From | Date | Subject | |
---|---|---|---|
Next Message | Devrim GUNDUZ | 2006-03-14 22:00:33 | Re: Clustered PostgreSQL |
Previous Message | Casey Duncan | 2006-03-14 21:42:34 | Re: Possible infinite loop in query using bitmap scans |