From: Junio C Hamano <gitster@pobox.com>
To: Jared Hance <jaredhance@gmail.com>
Cc: "Diego Elio Pettenò" <flameeyes@gmail.com>
Cc: Anders Kaseorg <andersk@MIT.EDU>, git@vger.kernel.org
Subject: Re: [PATCH] imap-send: link against libcrypto for HMAC and others
Date: Tue, 07 Dec 2010 18:12:00 -0800 [thread overview]
Message-ID: <7vd3pdm2rz.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <20101208015144.GA4868@localhost.localdomain> (Jared Hance's message of "Tue\, 7 Dec 2010 20\:51\:44 -0500")
Jared Hance <jaredhance@gmail.com> writes:
>> You are both correct; the point of NO_OPENSSL is not to link with anything
>> from openssl suite, so we need a separate mechanism to address this.
>>
>> Anders, wouldn't this be a better fix for NO_OPENSSL build, than reverting
>> a fix for an incorrect ld invocation?
>
> Could we get this fixup patch into master? Leaving the original patch
> in without it doesn't seem like a good idea when it breaks the build.
That depends on what Diego and Anders would say/report, and that is why
their address were on To/Cc in the message you are replying to. Why did
you cull Cc from your message?
One thing I do not like about it is that the "fixup" is ugly. It makes
people expect to add $(LIB_4_CRYPTO) on their linker command line to get a
correct linking with -lcrypto library, when all it does is _not_ to link
with -lcrypto at all, so whatever program that uses it needs to know about
NO_OPENSSL and refrain from using the symbols from that library.
next prev parent reply other threads:[~2010-12-08 2:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-24 13:55 [PATCH] imap-send: link against libcrypto for HMAC and others Diego Elio Pettenò
2010-11-24 20:01 ` Junio C Hamano
2010-11-24 20:03 ` Diego Elio Pettenò
2010-12-06 5:28 ` Anders Kaseorg
2010-12-06 5:39 ` Diego Elio Pettenò
2010-12-06 6:06 ` Jonathan Nieder
2010-12-06 6:11 ` Junio C Hamano
2010-12-08 1:51 ` Jared Hance
2010-12-08 2:12 ` Junio C Hamano [this message]
2010-12-08 4:53 ` Anders Kaseorg
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=7vd3pdm2rz.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=flameeyes@gmail.com \
--cc=jaredhance@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).