From: <rsbecker@nexbridge.com>
To: <rsbecker@nexbridge.com>, "'Taylor Blau'" <me@ttaylorr.com>
Cc: <git@vger.kernel.org>
Subject: RE: [BUG] Re: Git 2.35.0-rc0
Date: Tue, 11 Jan 2022 07:51:11 -0500 [thread overview]
Message-ID: <011a01d806e9$ec33e440$c49bacc0$@nexbridge.com> (raw)
In-Reply-To: <010d01d8069e$8d330480$a7990d80$@nexbridge.com>
On January 10, 2022 10:52 PM, Taylor Blau wrote:
> On January 10, 2022 10:00 PM, Taylor Blau wrote:
> > On Mon, Jan 10, 2022 at 09:57:57PM -0500, rsbecker@nexbridge.com
> > wrote:
> > > > If your system doesn't have a modern-ish zlib, you may try
> > > > building with that knob, or upgrading your system's copy of zlib.
> > > > And if NonStop doesn't have a modern zlib available at all, we
> > > > should modify the NonStop section of config.mak.uname.
> > >
> > > There is no provision in reftable/block.c to avoid using
> > > uncompress2, so the knob will not help. Our zlibc is not that recent
> > > (as in it does not have uncompress2) and we cannot make the 2.35.0
> > > timeframe to upgrade it. The current zlib seems to require gcc and
> > > is very difficult to port at this stage. This is a blocker situation.
> >
> > NO_UNCOMPRESS2 does not avoid calling uncompress2, but instead
> > compiles a copy-and-pasted implementation in compat/ so that the function
> is available.
> >
> > Looking through it, I can't imagine that it wouldn't compile just fine
> > even on NonStop.
> >
> > Have you tried building with NO_UNCOMPRESS2?
>
> The patch for NonStop to make this compile is as follows. Test is running - will
> be 2 days:
>
> diff --git a/config.mak.uname b/config.mak.uname index
> a3a779327f..9b3e9bff5f 100644
> --- a/config.mak.uname
> +++ b/config.mak.uname
> @@ -576,6 +576,7 @@ ifeq ($(uname_S),NONSTOP_KERNEL)
> NO_SETENV = YesPlease
> NO_UNSETENV = YesPlease
> NO_MKDTEMP = YesPlease
> + NO_UNCOMPRESS2 = YesPlease
> # Currently libiconv-1.9.1.
> OLD_ICONV = UnfortunatelyYes
> NO_REGEX = NeedsStartEnd
>
> Could we get that into rc1?
The above is working. We're at t2015 right now. Much relieved.
--Randall
next prev parent reply other threads:[~2022-01-11 12:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-11 2:20 [BUG] Re: Git 2.35.0-rc0 rsbecker
2022-01-11 2:52 ` Taylor Blau
2022-01-11 2:57 ` rsbecker
2022-01-11 3:00 ` Taylor Blau
2022-01-11 3:03 ` rsbecker
2022-01-11 3:51 ` rsbecker
2022-01-11 12:51 ` rsbecker [this message]
2022-01-11 19:53 ` Taylor Blau
2022-01-11 20:39 ` rsbecker
2022-01-12 19:18 ` Junio C Hamano
2022-01-12 19:21 ` Taylor Blau
2022-01-13 13:21 ` Ævar Arnfjörð Bjarmason
2022-01-13 18:03 ` Junio C Hamano
[not found] <00ef01d80691$82df3380$889d9a80$@nexbridge.com>
2022-01-11 2:25 ` 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='011a01d806e9$ec33e440$c49bacc0$@nexbridge.com' \
--to=rsbecker@nexbridge.com \
--cc=git@vger.kernel.org \
--cc=me@ttaylorr.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).