Re: ./configure --with-openssl=path fails

From: Wes <wespvp(at)syntegra(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-general(at)postgresql(dot)org>
Subject: Re: ./configure --with-openssl=path fails
Date: 2006-01-11 06:24:35
Message-ID: BFEA00C3.1C357%wespvp@syntegra.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 1/6/06 2:47 PM, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

>> ./configure --with-openssl=path
>> This no longer works with 8.x. See:
>> <http://archives.postgresql.org/pgsql-committers/2003-11/msg00278.php>
>> What is the correct way to work around this restriction?
>
> 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 way
to solve this? I think the previous --with-openssl=path set the search path
so the libraries would always be found.

Wes

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Gevik 2006-01-11 09:53:56 Recommend IDE for PG Development
Previous Message A. Kretschmer 2006-01-11 06:00:06 Re: Array as a parameter to stored procedure.