From: David Aguilar <davvid@gmail.com>
To: Eric Sunshine <sunshine@sunshineco.com>
Cc: Junio C Hamano <gitster@pobox.com>,
Git List <git@vger.kernel.org>,
Jonathan Nieder <jrnieder@gmail.com>
Subject: Re: [PATCH v3 3/3] cache.h: eliminate SHA-1 deprecation warnings on OS X 10.8
Date: Mon, 13 May 2013 01:04:30 -0700 [thread overview]
Message-ID: <CAJDDKr5Y0XZfiV8Xpm0KpbB5_nxAexBMhYnV5ZMwOznNSJ4PbA@mail.gmail.com> (raw)
In-Reply-To: <CAPig+cRGkhA9xd0d3QG3kGZTV3EXe-_S0j0x1+NkucNg_NU4dQ@mail.gmail.com>
On Mon, May 13, 2013 at 12:55 AM, Eric Sunshine <sunshine@sunshineco.com> wrote:
> On Mon, May 13, 2013 at 3:20 AM, David Aguilar <davvid@gmail.com> wrote:
>> Mac OS X Mountain Lion prints warnings when building git:
>>
>> warning: 'SHA1_Init' is deprecated
>> (declared at /usr/include/openssl/sha.h:121)
>>
>> Silence the warnings by using the Common Digest SHA-1
>> functions for SHA1_Init(), SHA1_Update(), and SHA1_Final().
>>
>> Add a COMMON_DIGEST_SHA1 option to the Makefile to allow
>> choosing this implementation and define it by default on Darwin.
>>
>> Define COMMON_DIGEST_FOR_SHA1 to enable the OpenSSL compatibility
>> macros in CommonDigest.h.
>>
>> Helped-by: Eric Sunshine <sunshine@sunshineco.com>
>> Signed-off-by: David Aguilar <davvid@gmail.com>
>> ---
>> Here's a replacement patch for what's in pu.
>> This version uses the built-in #defines and can thus avoid
>> touching cache.h.
>>
>> Makefile | 6 ++++++
>> 1 file changed, 6 insertions(+)
>>
>> diff --git a/Makefile b/Makefile
>> index 25282b4..9d174b9 100644
>> --- a/Makefile
>> +++ b/Makefile
>> @@ -1055,6 +1055,7 @@ ifeq ($(uname_S),Darwin)
>> endif
>> endif
>> COMMON_DIGEST_HMAC = YesPlease
>> + COMMON_DIGEST_SHA1 = YesPlease
>> NO_REGEX = YesPlease
>> PTHREAD_LIBS =
>> endif
>> @@ -1390,10 +1391,15 @@ ifdef PPC_SHA1
>> LIB_OBJS += ppc/sha1.o ppc/sha1ppc.o
>> LIB_H += ppc/sha1.h
>> else
>> +ifdef COMMON_DIGEST_SHA1
>> + BASIC_CFLAGS += -DCOMMON_DIGEST_FOR_SHA1=1
>
> This is incorrect. As noted in my previous email, you need to define
> COMMON_DIGEST_FOR_OPENSSL, not COMMON_DIGEST_FOR_SHA1, in order for
> CommonDigest.h to provide the OpenSSL defines magically. Thus:
>
> s/COMMON_DIGEST_FOR_SHA1=1/COMMON_DIGEST_FOR_OPENSSL/
Yes, you're right. Strangely, it compiled just fine either way which
is why I hadn't noticed.
I'll resend along w/ a replacement for 2/3 to drop the "=1" in the -D
definition.
--
David
prev parent reply other threads:[~2013-05-13 8:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-13 7:20 [PATCH v3 3/3] cache.h: eliminate SHA-1 deprecation warnings on OS X 10.8 David Aguilar
2013-05-13 7:55 ` Eric Sunshine
2013-05-13 8:04 ` David Aguilar [this message]
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=CAJDDKr5Y0XZfiV8Xpm0KpbB5_nxAexBMhYnV5ZMwOznNSJ4PbA@mail.gmail.com \
--to=davvid@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.com \
--cc=sunshine@sunshineco.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).