From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: "Carlo Marcelo Arenas Belón" <carenas@gmail.com>
Cc: rsbecker@nexbridge.com, 'Junio C Hamano' <gitster@pobox.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: Tue, 5 Apr 2022 08:10:28 +0000 [thread overview]
Message-ID: <Ykv5dCEv/gl7aHMq@camp.crustytoothpaste.net> (raw)
In-Reply-To: <20220405042826.56vyilttx3lo4scv@carlos-mbp.lan>
[-- Attachment #1: Type: text/plain, Size: 1264 bytes --]
On 2022-04-05 at 04:28:26, Carlo Marcelo Arenas Belón wrote:
> Subject: [PATCH] git-compat-util: really support openssl as a source of entropy
>
> 05cd988dce5 (wrapper: add a helper to generate numbers from a CSPRNG,
> 2022-01-17), configure openssl as the source for entropy in NON-STOP
> but doesn't add the needed header or link options.
>
> Since the only system that is configured to use openssl as a source
> of entropy is NON-STOP, add the header unconditionally, and -lcrypto
> to the list of external libraries.
>
> An additional change is required to make sure a NO_OPENSSL=1 build
> will be able to work as well (tested on Linux with a modified value
> of CSPRNG_METHOD = openssl), and the more complex logic that allows
> for compatibility with APPLE_COMMON_CRYPTO or allowing for simpler
> ways to link (without libssl) has been punted for now.
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!"
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.
--
brian m. carlson (he/him or they/them)
Toronto, Ontario, CA
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2022-04-05 8:23 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 [this message]
2022-04-05 22:47 ` Carlo Arenas
2022-04-05 23:09 ` rsbecker
2022-04-06 16:04 ` Junio C Hamano
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=Ykv5dCEv/gl7aHMq@camp.crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--cc=carenas@gmail.com \
--cc=git-packagers@googlegroups.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=rsbecker@nexbridge.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).