Bugs item #3029420, was opened at 2010-07-14 11:46
Message generated for change (Comment added) made by kdekker
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100976&aid=3029420&group_id=976

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: compile or build problem
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: kdekker (kdekker)
Assigned to: Daniel Stenberg (bagder)
Summary: clash with 64-bit build and openssl1.0.0a

Initial Comment:
For some reason, open SSL changed their output directories for soe 64-bit builds.
If prefix is x (used during configure of openSSL), the static libraries (.a files) and pkgconfig subdirectory are put in:
Solaris: x/lib/66
HPUX IA64: x/lib/hpux64
HPUX PA-risc; x/lib/pa20_64
Linux: x/lib64

Although these namings are similar to how the involved OS put their system libs under /lib, cURL configure can't handle this. Also, if -Lx/lib was specified during linking/compilation, the compiler/linker was not able to find e.g. libssl.a or libcrypto.a.

The cURL configure output points already to an error/warning:
checking if GSSAPI support is requested... no
configure: PKG_CONFIG_LIBDIR will be set to "/vobs/obj.SOL10/thirdparty/OpenSSL/64bit/lib/pkgconfig"
checking for CRYPTO_lock in -lcrypto... no
checking for CRYPTO_add_lock in -lcrypto... no
configure: WARNING: zlib disabled
configure: WARNING: SSL disabled, you will not be able to use HTTPS, FTPS, NTLM and more.
configure: WARNING: Use --with-ssl, --with-gnutls, --with-polarssl or --with-nss to address this.
checking default CA cert bundle/path... no

I understand why openSSL changes the output directory (espcially of you need both 32 and 64 bit SSL together in one /usr/local/ssl directory), however, I don't know whether cURL should be able to handle this.

Unfortunatelly, I don't have pkg-config on a lot of systems. Either specifying PKG_CONFIG_PATH or --with-ssl=PATH does not work. In case if I specify --with-ssl=x/lib/64, then the include files are not found (which are still in x/include). If you know a workaround for this problem, it would be great.

Feel free to ask for more information, if needed.

----------------------------------------------------------------------

>Comment By: kdekker (kdekker)
Date: 2010-07-14 11:52

Message:
openssl0.9.8k still uses x/lib, also for all 64bit builds.
The open ssl CHANGES file did not tell when this behavior was introduced
(or I missed something)

----------------------------------------------------------------------

You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100976&aid=3029420&group_id=976
Received on 2010-07-14