curl-library
Re: Compilation issue: linking to openssl with absolute path?
Date: Mon, 06 Oct 2014 15:42:15 +0200
Hi there,
On 03/10/2014 17:03, dev wrote:
>> Can OP post ./configure command line being used?
Here goes:
LDFLAGS=" -L/home/smokey/projects/optware/syno-x86_64/staging/opt/lib
-Wl,-rpath,/opt/lib
-Wl,-rpath-link,/home/smokey/projects/optware/syno-x86_64/staging/opt/lib -lssl"
\
./configure \
--build=x86_64-pc-linux-gnu \
--host=x86_64-pc-linux-gnu \
--target=x86_64-pc-linux-gnu \
--prefix=/opt \
--disable-thread \
--enable-shared \
--disable-static \
--enable-ares \
--enable-cookies \
--enable-crypto-auth \
--enable-nonblocking \
--enable-file \
--enable-ftp \
--enable-http \
--enable-ipv6 \
--enable-tftp \
--disable-nls \
--disable-ares \
--disable-dict \
--disable-debug \
--disable-gopher \
--disable-ldap \
--disable-manual \
--disable-telnet \
--disable-verbose \
--with-random="/dev/urandom" \
--with-ssl="/home/smokey/projects/optware/syno-x86_64/staging" \
--without-gnutls \
--without-krb4 \
--without-libidn \
--with-zlib="/home/smokey/projects/optware/syno-x86_64/staging" \
--with-ca-bundle=/opt/share/curl/curl-ca-bundle.crt
> Just a head up, if you can not rely on your installs being in the same
> PATH
I don't know whether that was directed at me so I'll answer anyway. My
problem is not the OpenSSL being installed in the wrong path.
My problem is that I am building for a different target with identical
arch (x86_64), which I believe causes configure to fetch the system's
OpenSSL instead of the staging one, which path is passed as a parameter
to --with-ssl (see above).
If I edit the configure script to initialize cross_compiling=yes, it
does compile and link against the staged libssl.
Is there a better way to achieve this than by modifying the configure
script?
Cheers
-- Romain Rivière ------------------------------------------------------------------- List admin: http://cool.haxx.se/list/listinfo/curl-library Etiquette: http://curl.haxx.se/mail/etiquette.htmlReceived on 2014-10-06