Re: [GENERAL] ./configure --with-openssl=path fails

Wes <[EMAIL PROTECTED]> writes: > On 1/6/06 2:47 PM, "Tom Lane" <[EMAIL PROTECTED]> wrote: >> Use --with-includes and --with-libraries as needed. > That doesn't get the library paths into the binary. If the libraries are > not in the default system search path, the user is screwed. Is there a wa

Re: [GENERAL] ./configure --with-openssl=path fails

On 1/6/06 2:47 PM, "Tom Lane" <[EMAIL PROTECTED]> wrote: >> ./configure --with-openssl=path >> This no longer works with 8.x. See: >> >> What is the correct way to work around this restriction? > > Use --with-includes and --

Re: [GENERAL] ./configure --with-openssl=path fails

On 1/6/06 2:47 PM, "Tom Lane" <[EMAIL PROTECTED]> wrote: >> ./configure --with-openssl=path >> This no longer works with 8.x. See: >> >> What is the correct way to work around this restriction? > > Use --with-includes and --

Re: [GENERAL] ./configure --with-openssl=path fails

Wes <[EMAIL PROTECTED]> writes: > ./configure --with-openssl=path > This no longer works with 8.x. See: > > What is the correct way to work around this restriction? Use --with-includes and --with-libraries as needed.

[GENERAL] ./configure --with-openssl=path fails

Because of our build environment, we need to build PostgreSQL specifying the location of the openssl libraries to insure everyone is using the same libraries, regardless of the system software is built and executed on. At 7.4.5, we used: ./configure --with-openssl=path This no longer works with