From: Dennis Clarke <dclarke@blastwave.org>
To: Jeff King <peff@peff.net>, Junio C Hamano <gitster@pobox.com>
Cc: Jeffrey Walton <noloader@gmail.com>, git@vger.kernel.org
Subject: Re: minor patch required to compile git 2.26.1 on Oracle Solaris 10 with Oracle Studio
Date: Wed, 22 Apr 2020 20:09:46 -0400 [thread overview]
Message-ID: <f0beedfb-b50b-51b9-d996-155e0178a90d@blastwave.org> (raw)
In-Reply-To: <20200422081156.GB464427@coredump.intra.peff.net>
On 2020-04-22 04:11, Jeff King wrote:
> On Wed, Apr 22, 2020 at 04:09:50AM -0400, Jeff King wrote:
>
>> Which implies that NO_INET_NTOP should not be set in the first place.
>> I think this is the same issue discussed in:
>>
>> https://lore.kernel.org/git/CAH8yC8m3JFvEcfFF3z1rrRnEPK-adHGObmkOhNZiph7QJKUWqA@mail.gmail.com/
>>
>> with a patch (which needs at least a signoff added) in:
>>
>> https://lore.kernel.org/git/CAH8yC8kaWXbN+RYMJnM9em7KKW54+N07JtyS1MZk0qppD=m2BA@mail.gmail.com/
>>
>> Dennis, does building with:
>>
>> make NO_INET_NTOP= NO_INET_PTON=
>>
I will give that a try today and see what happens. There seems to be a
2.26.2 release from yesterday and may as well get that going. What was
the changelog reason for the bump from 2.26.1 to 2.26.2 ?
Dennis
next prev parent reply other threads:[~2020-04-23 0:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-19 4:52 minor patch required to compile git 2.26.1 on Oracle Solaris 10 with Oracle Studio Dennis Clarke
2020-04-19 5:35 ` Junio C Hamano
2020-04-22 8:09 ` Jeff King
2020-04-22 8:11 ` Jeff King
2020-04-23 0:09 ` Dennis Clarke [this message]
2020-04-23 5:41 ` Kevin Daudt
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=f0beedfb-b50b-51b9-d996-155e0178a90d@blastwave.org \
--to=dclarke@blastwave.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=noloader@gmail.com \
--cc=peff@peff.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 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).