From: Junio C Hamano <gitster@pobox.com>
To: "brian m. carlson" <sandals@crustytoothpaste.net>
Cc: "Carlo Marcelo Arenas Belón" <carenas@gmail.com>,
rsbecker@nexbridge.com,
"'Git Mailing List'" <git@vger.kernel.org>,
git-packagers@googlegroups.com
Subject: Re: [ANNOUNCE] Git v2.36.0-rc0 - Build failure on NonStops
Date: Wed, 06 Apr 2022 09:04:20 -0700 [thread overview]
Message-ID: <xmqqzgkyyz97.fsf@gitster.g> (raw)
In-Reply-To: <Ykv5dCEv/gl7aHMq@camp.crustytoothpaste.net> (brian m. carlson's message of "Tue, 5 Apr 2022 08:10:28 +0000")
"brian m. carlson" <sandals@crustytoothpaste.net> writes:
> I didn't consider the case that we had NO_OPENSSL=1 because it seems a
> bit bizarre to say, "No, I don't want OpenSSL—oh, wait, I do want
> OpenSSL!"
Indeed ;-).
> This patch also didn't seem necessary for me on Linux when I tested, but
> of course it might be necessary on some systems, so if it fixes things,
> I'm in favour.
I think I've seen the breakage myself when I tried to force
CSPRNG_METHOD = openssl in my build. Let's take the patch as-is for
now.
next prev parent reply other threads:[~2022-04-06 17:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-04 22:30 [ANNOUNCE] Git v2.36.0-rc0 - Build failure on NonStops rsbecker
2022-04-04 22:32 ` Junio C Hamano
2022-04-04 22:40 ` rsbecker
2022-04-05 0:26 ` Carlo Marcelo Arenas Belón
2022-04-05 0:54 ` Carlo Marcelo Arenas Belón
2022-04-05 2:59 ` rsbecker
2022-04-05 4:28 ` Carlo Marcelo Arenas Belón
2022-04-05 8:10 ` brian m. carlson
2022-04-05 22:47 ` Carlo Arenas
2022-04-05 23:09 ` rsbecker
2022-04-06 16:04 ` Junio C Hamano [this message]
2022-04-05 12:33 ` rsbecker
2022-04-05 1:56 ` rsbecker
2022-04-06 16:14 ` Junio C Hamano
2022-04-06 16:23 ` rsbecker
2022-04-06 19:37 ` Junio C Hamano
2022-04-06 22:32 ` rsbecker
2022-04-06 20:01 ` rsbecker
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=xmqqzgkyyz97.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=carenas@gmail.com \
--cc=git-packagers@googlegroups.com \
--cc=git@vger.kernel.org \
--cc=rsbecker@nexbridge.com \
--cc=sandals@crustytoothpaste.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.