git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] imap-send: link against libcrypto for HMAC and others

From
Junio C Hamano <gitster@pobox.com>
Date
Dec 8, 2010, 02:12 UTC
Message-ID
<7vd3pdm2rz.fsf@alter.siamese.dyndns.org>
In-Reply-To
<20101208015144.GA4868@localhost.localdomain>
Jared Hance <jaredhance@gmail.com> writes:
Show 8 quoted lines
>> 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.

Previous: Jared HanceNext: Anders Kaseorg
Message 9 of 10 in “imap-send: link against libcrypto for HMAC and others”
  1. imap-send: link against libcrypto for HMAC and othersDiego Elio Pettenò, Nov 24, 2010
  2. Junio C HamanoNov 24, 2010
  3. imap-send: link against libcrypto for HMAC and othersDiego Elio Pettenò, Nov 24, 2010
  4. Anders KaseorgDec 6, 2010
  5. Diego Elio PettenòDec 6, 2010
  6. Jonathan NiederDec 6, 2010
  7. Junio C HamanoDec 6, 2010
  8. Jared HanceDec 8, 2010
  9. Junio C HamanoDec 8, 2010
  10. Anders KaseorgDec 8, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.