From: Remi Pommarel <repk@triplefau.lt>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Brandon Casey <drafnel@gmail.com>,
Jeff King <peff@peff.net>, Jonathan Nieder <jrnieder@gmail.com>
Subject: Re: [PATCH] Makefile: Change library order for static linking
Date: Fri, 18 Sep 2015 09:17:14 +0200 [thread overview]
Message-ID: <20150918071525.GA482@cruxbox> (raw)
In-Reply-To: <xmqq7fnoitra.fsf@gitster.mtv.corp.google.com>
On Thu, Sep 17, 2015 at 03:08:25PM -0700, Junio C Hamano wrote:
> That is, for most people, linking with -lcrypto was sufficient, but
> some people needed to grab things from -lssl when they need to do
> so, because things in -lcrypto referred to what was only in -lssl.
Oh I see what you mean, I misinterpreted what NEEDS_SSL_WITH_CRYPTO
does.
The problem on static compiled target is that libcurl.a got linked with
libssl symbols. The proper variable I should have used is
NEEDS_SSL_WITH_CURL. But this variable is not setted on Linux and not
configurable, this is why I wrongly used NEEDS_SSL_WITH_CRYPTO.
I see several ways to fix static compilation:
1) Make NEED_SSL_WITH_CURL overridable by configure (the same
way NEEDS_SSL_WITH_CRYPTO is). Then static target should run
"NEED_SSL_WITH_CURL=YesPlease ./configure"
2) Make configure know that static compilation is asked (ie
./configure --static) and automatically set NEED_SSL_WITH_CURL.
3) Use "curl-config --static-libs" to fill CURL_LIBCURL in
Makefile when ones use "./configure --static".
next prev parent reply other threads:[~2015-09-18 7:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-17 21:12 [PATCH] Makefile: Change library order for static linking Remi Pommarel
2015-09-17 19:25 ` Eric Sunshine
2015-09-17 21:31 ` Remi Pommarel
2015-09-17 19:51 ` Junio C Hamano
2015-09-17 21:20 ` Remi Pommarel
2015-09-17 22:08 ` Junio C Hamano
2015-09-18 7:17 ` Remi Pommarel [this message]
2015-09-21 17:09 ` Junio C Hamano
2015-09-22 20:37 ` Remi Pommarel
2015-09-22 21:30 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150918071525.GA482@cruxbox \
--to=repk@triplefau.lt \
--cc=drafnel@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.com \
--cc=peff@peff.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.