From: | Dave Page <dpage(at)pgadmin(dot)org> |
---|---|
To: | "Andreas 'ads' Scherbaum" <adsmail(at)wars-nicht(dot)de> |
Cc: | pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
Subject: | Re: crypto library is not installed |
Date: | 2014-03-03 13:44:52 |
Message-ID: | CA+OCxowtzfDkJf_=hqXwy+r34utjM9hP4CHrD=xChDsp98UoFw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
On Mon, Mar 3, 2014 at 1:05 PM, Andreas 'ads' Scherbaum
<adsmail(at)wars-nicht(dot)de> wrote:
> On 03/03/2014 11:32 AM, Dave Page wrote:
>>
>> On Mon, Mar 3, 2014 at 10:20 AM, Andreas 'ads' Scherbaum
>> <adsmail(at)wars-nicht(dot)de> wrote:
>>>
>>>
>>> Yes, I know how to fix this. My question is: why is "configure" not
>>> checking
>>> for this library, when it is required to build pgAdmin3?
>>
>>
>> Noone wrote the code I guess. Patches welcome :-)
>
>
> Just checking the code: why is it even requiring "crypto" when compiling
> without --with-openssl?
That's actually the likely reason why we don't do that test. It seems
to be required because we're linking with libpq which is linked with
OpenSSL, apps linking to it (on some platforms) also need to link with
libcypto. It may also be that an element of bitrot has crept into that
configure option - I very much doubt anyone has tested without SSL
support in a long time.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Willy-Bas Loos | 2014-03-03 22:29:52 | building pgadmin4 |
Previous Message | Andreas 'ads' Scherbaum | 2014-03-03 13:05:13 | Re: crypto library is not installed |