From: Taylor Blau <me@ttaylorr.com>
To: Patrick Steinhardt <ps@pks.im>
Cc: Freya Starshade <saoirse@axiom-networks.org>, git@vger.kernel.org
Subject: Re: [Resend] Re: Git build failure: v2.47.0 on Solaris 10 SPARC64
Date: Mon, 21 Oct 2024 17:11:06 -0400 [thread overview]
Message-ID: <ZxbDaiaSUgRa3WYd@nand.local> (raw)
In-Reply-To: <ZxYgDu2vt-qDqmqr@pks.im>
On Mon, Oct 21, 2024 at 11:34:06AM +0200, Patrick Steinhardt wrote:
> > > Could you maybe also send the output of `./configure`? We do have a
> > > check in "configure.ac" that tries to find out whether your system has
> > > `inet_ntop()` or not. Maybe it is misdetecting the availability of that
> > > function on your platform and thus declares the `NO_INET_NTOP` variable,
> > > which causes us to pull in compat code.
> > >
> > > Out of curiosity, did you try running `make` without first running
> > > `./configure`? Many platforms should work alright without having to run
> > > autoconf first, but given that your platform is a more on the esoteric
> > > side I wouldn't be surprised if things didn't work there.
>
> [snip]
> > checking for inet_ntop... no
> > checking for inet_ntop in -lresolv... no
> > checking for inet_pton... no
> > checking for inet_pton in -lresolv... no
>
> So yes, indeed, your `inet_ntop()` isn't detected. Does that function
> require any additional libraries on your platform? Searching for this on
> the internet quickly brings me to... a [thread] from our own mailing
> list. Looks like that patch never landed.
Thanks for digging.
Thanks,
Taylor
prev parent reply other threads:[~2024-10-21 21:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-21 5:56 Git build failure: v2.47.0 on Solaris 10 SPARC64 Freya Starshade
2024-10-21 8:56 ` Patrick Steinhardt
[not found] ` <966457d3-c6f6-4028-bd28-da73a0296679@axiom-networks.org>
2024-10-21 9:34 ` [Resend] " Patrick Steinhardt
2024-10-21 21:11 ` Taylor Blau [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=ZxbDaiaSUgRa3WYd@nand.local \
--to=me@ttaylorr.com \
--cc=git@vger.kernel.org \
--cc=ps@pks.im \
--cc=saoirse@axiom-networks.org \
/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.