From: <rsbecker@nexbridge.com>
To: <rsbecker@nexbridge.com>, "'Junio C Hamano'" <gitster@pobox.com>
Cc: <git@vger.kernel.org>
Subject: RE: [PATCH v1] Modify NonStop configuration to disable uncompress2
Date: Wed, 12 Jan 2022 18:52:45 -0500 [thread overview]
Message-ID: <004601d8080f$81edb300$85c91900$@nexbridge.com> (raw)
In-Reply-To: <003d01d807fc$b9217400$2b645c00$@nexbridge.com>
On January 12, 2022 4:38 PM, I wrote:
> On January 12, 2022 3:17 PM, Junio wrote:
> > <rsbecker@nexbridge.com> writes:
> >
> > > Modify NonStop configuration to disable uncompress2.
> > >
> > > The zlib version available on NonStop x86/ia64 does not contain the
> > > uncompress2()
> > > Procedure.
> > >
> > > Signed-off-by: Randall S. Becker <rsbecker@nexbridge.com>
> > > ---
> > > config.mak.uname | 1 +
> > > 1 file changed, 1 insertion(+)
> >
> > I'll lift your s-o-b from this patch and use it in
> <xmqqzgo0u5j7.fsf@gitster.g>, as the
> > patch part didn't apply.
> >
> > Thanks.
> >
> > >
> > > 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
> > > --
> > > 2.34.1
With this patch, rc0 passes on NonStop ia64.
Thanks,
Randall
prev parent reply other threads:[~2022-01-12 23:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-12 19:56 [PATCH v1] Modify NonStop configuration to disable uncompress2 rsbecker
2022-01-12 20:17 ` Junio C Hamano
2022-01-12 21:38 ` rsbecker
2022-01-12 23:52 ` rsbecker [this message]
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='004601d8080f$81edb300$85c91900$@nexbridge.com' \
--to=rsbecker@nexbridge.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).