All of lore.kernel.org
 help / color / mirror / Atom feed
From: <rsbecker@nexbridge.com>
To: "'Carlo Arenas'" <carenas@gmail.com>,
	"'brian m. carlson'" <sandals@crustytoothpaste.net>,
	"'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 19:09:28 -0400	[thread overview]
Message-ID: <03f101d84942$36be25d0$a43a7170$@nexbridge.com> (raw)
In-Reply-To: <CAPUEspjAiXKz00VgP16RRA+ZKYpG0QjpU4XxwJXYnZm+MQwwqg@mail.gmail.com>

On April 5, 2022 6:48 PM, Carlo Arenas wrote:
>To: brian m. carlson <sandals@crustytoothpaste.net>; Carlo Marcelo Arenas Belón
><carenas@gmail.com>; 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
>
>On Tue, Apr 5, 2022 at 1:10 AM brian m. carlson <sandals@crustytoothpaste.net>
>wrote:
>> 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!"
>
>NO_OPENSSL is definitely strange, for example in macOS it means: do not link with
>openssl if it comes from homebrew or macports, but maybe use the one that
>comes with the system, which happens to be based on openssl anyway (based on
>libressl, boringssl, or even a really old version of openssl, depending on which
>version of the OS you got).
>
>Either way, the choice of using the openssl function this requires could work with
>any of those if provided with the right linker settings, but it doesn't seem worth
>the trouble to do, especially not for rc0.
>
>> 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.
>
>Not sure if the required changes got somehow dropped in one of the rebases
>after your tests, but it definitely didn't work for me when tested on Linux (using
>debian stable or sid) and I can't see how it would work unless the crypto library is
>pulled in some other way, and even in that case the lack of the header should
>break, at least with DEVELOPER=1.

I had to be explicit and override the LDFLAGS to include -lcrypto and -lssl at least for git-daemon with the wrapper.c patch. Testing is still going - currently at t5531 on the ia64 NonStop variant without problems. I deliberately picked the more finicky of the two systems since x86 uses a slightly simpler OpenSSL with the x86 hardware randomizer.


  reply	other threads:[~2022-04-06  5:07 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 [this message]
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='03f101d84942$36be25d0$a43a7170$@nexbridge.com' \
    --to=rsbecker@nexbridge.com \
    --cc=carenas@gmail.com \
    --cc=git-packagers@googlegroups.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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.