cURL / Mailing Lists / curl-library / Single Mail


Re: curl-7.29.0: 'curl' executable fails to link against custom-built OpenSSL

From: Jeroen DR <>
Date: Mon, 04 Mar 2013 21:58:46 +0100

You're right, does contain such a line:

$ cat lib/
dependency_libs=' -lssl -lcrypto -lz -lrt - L/home/ct-dist/myopenssl/lib'

Still though, these flags are apparently not being included on the
final command line that libtool (?) executes.

And yet, the -L/home/ct-dist/myopenssl/lib bit*is* there, which could
only have come from `pkg-config --libs openssl`, which I know to also
include the -lssl -lcrypto bits. Is it slicing and dicing? What's
going on?

(I have much to learn about libtool, forgive any ignorance).

> On Mon, Mar 4, 2013 at 4:34 PM, Jeroen De Ridder
> <> wrote:
>> curl_LDADD = $(top_builddir)/lib/ -lz -lrt
>> #curl_LDADD = $(top_builddir)/lib/ -lidn -lssl -lcrypto
>> -lssl -lcrypto -lz -lrt
>> So evidently at one point the -lssl -lcrypto flags were there, but
>> they were commented out and removed. What happened? How come they
>> aren't in there anymore?
> That's presumably because the file includes something like
> this (taken from a recent libcurl build I did):
> ..
> # Libraries that this one depends upon.
> dependency_libs=' -lidn -lrtmp -lssh2 -lssl -lcrypto -lldap -lz -lrt'
> ..
> which should make the linker load those additional libraries automatically.
> -Tor
> This e-mail and any attachment contain KONGSBERG information which may be
> proprietary, confidential or subject to export regulations, and is only meant
> for the intended recipient(s). Any disclosure, copying, distribution or use is
> prohibited, if not otherwise explicitly agreed with KONGSBERG. If received in
> error, please delete it immediately from your system and notify the sender
> properly.
> -------------------------------------------------------------------
> List admin:
> Etiquette:

List admin:
Received on 2013-03-04