From: Junio C Hamano <gitster@pobox.com>
To: Remi Pommarel <repk@triplefau.lt>
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: Thu, 17 Sep 2015 15:08:25 -0700 [thread overview]
Message-ID: <xmqq7fnoitra.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20150917212016.GF606@cruxbox> (Remi Pommarel's message of "Thu, 17 Sep 2015 23:20:16 +0200")
Remi Pommarel <repk@triplefau.lt> writes:
> On Thu, Sep 17, 2015 at 12:51:18PM -0700, Junio C Hamano wrote:
>> IIRC historically the division between ssl and crypto was messy.
>> Especially, I am not sure if the change to NEEDS_SSL_WITH_CRYPTO
>> in this patch is correct for platforms that require that macro
>> defined.
>
> I think it is correct as anywhere else in Makefile the order is ssl
> first then crypto (from Makefile:1047):
IIRC, NEEDS_SSL_WITH_CRYPTO was invented for people whose platform
needed that to be different
597c9cc5 (Flatten tools/ directory to make build procedure simpler.,
2005-09-07) has this bit:
+ifdef NEEDS_SSL_WITH_CRYPTO
+ LIB_4_CRYPTO = -lcrypto -lssl
+else
+ LIB_4_CRYPTO = -lcrypto
+endif
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.
Are you on such a platform? If so can you test these both ways and
make sure you are not breaking things for those on such a platform?
next prev parent reply other threads:[~2015-09-17 22:08 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 [this message]
2015-09-18 7:17 ` Remi Pommarel
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=xmqq7fnoitra.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=drafnel@gmail.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=peff@peff.net \
--cc=repk@triplefau.lt \
/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.