Lists: | pgsql-testers |
---|
From: | Lou Picciano <LouPicciano(at)comcast(dot)net> |
---|---|
To: | pgsql-testers(at)postgresql(dot)org |
Subject: | 9.0-beta3: configure does not find OpenSSL (1.0.0a) libcrypto in /usr/local/ssl |
Date: | 2010-07-13 18:07:26 |
Message-ID: | 5B7C158E-0CC2-41E3-A1E7-F65E35674EFB@comcast.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgsql-testers |
TEST REPORT]
[Release]: 9.0Beta3
[Test Type]: ./configure Source...
[Test]: Attempted ./configure on 9.0-beta3 source tree with various options...
[Platform]: Solaris 10 Sun4u Ultra Enterprise 450 Quad
[Parameters]: ./configure --with-openssl
[Failure]: Yes
[Results]: ./configure --with-openssl
configure: error: library 'crypto' is required for OpenSSL
-LOG OUTPUT:
checking whether to build with OpenSSL support... yes
...
checking for library containing crypt... none required
...
checking for CRYPTO_new_ex_data in -lcrypto... no
[Comments]: Again, this seems to be new behavior, as previous builds had been able to find OpenSSL without explicit direction to includes and libs.
After adding explicit options for includes and libs paths, configure does find OpenSSL AOK:
--with-includes=/usr/local/ssl/include \
--with-libs=/usr/local/ssl/lib \
From: | Josh Berkus <josh(at)agliodbs(dot)com> |
---|---|
To: | Lou Picciano <LouPicciano(at)comcast(dot)net> |
Cc: | pgsql-testers(at)postgresql(dot)org |
Subject: | Re: 9.0-beta3: configure does not find OpenSSL (1.0.0a) libcrypto in /usr/local/ssl |
Date: | 2010-07-18 14:28:53 |
Message-ID: | 4C430FA5.4080601@agliodbs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgsql-testers |
> *[Comments]:* Again, this seems to be new behavior, as previous builds
> had been able to find OpenSSL without explicit direction to includes and
> libs.
> After adding explicit options for includes and libs paths, configure
> does find OpenSSL AOK:
> --with-includes=/usr/local/ssl/include \
> --with-libs=/usr/local/ssl/lib \
Can you verify that it's not just a 64/32 bit issue again?
--
-- Josh Berkus
PostgreSQL Experts Inc.
http://www.pgexperts.com