All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Carlo Marcelo Arenas Belón" <carenas@gmail.com>
To: rsbecker@nexbridge.com
Cc: '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: Mon, 4 Apr 2022 17:26:10 -0700	[thread overview]
Message-ID: <20220405002610.27sgjva5wfryrcio@carlos-mbp.lan> (raw)
In-Reply-To: <034701d84875$030bfb40$0923f1c0$@nexbridge.com>

On Mon, Apr 04, 2022 at 06:40:35PM -0400, rsbecker@nexbridge.com wrote:
> On April 4, 2022 6:33 PM, Junio C Hamano wrote:
> >To: Randall S. Becker <rsbecker@nexbridge.com>
> >Cc: Git Mailing List <git@vger.kernel.org>; git-packagers@googlegroups.com
> >Subject: Re: [ANNOUNCE] Git v2.36.0-rc0 - Build failure on NonStops
> >
> >CSPRNG_METHOD?
> 
> We already have
> 
>         CSPRNG_METHOD = openssl
> 
> In the config for NonStop. Should that not have worked?

only if you are not telling your openssl to hide that function[1]

Carlo

[1] https://www.openssl.org/docs/manmaster/man3/RAND_bytes.html

  reply	other threads:[~2022-04-05  0:41 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 [this message]
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
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=20220405002610.27sgjva5wfryrcio@carlos-mbp.lan \
    --to=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 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.