archive mirror
 help / color / mirror / Atom feed
From: "brian m. carlson" <>
To: Jeffrey Walton <>
Cc: Git List <>
Subject: Re: Git 2.31.1, Solaris and error: conflicting types for 'inet_ntop'
Date: Sun, 28 Mar 2021 01:26:10 +0000	[thread overview]
Message-ID: <YF/> (raw)
In-Reply-To: <>

[-- Attachment #1: Type: text/plain, Size: 777 bytes --]

On 2021-03-28 at 01:04:32, Jeffrey Walton wrote:
> I see what happened... I stopped Autoreconfing so the
> changes were not picked up. The original configure is being used.
> I think Git is getting itself into that state.
> Without the Autoreconf, I was able to sidestep the issue with:
> if [[ "${IS_SOLARIS}" -eq 1 ]]; then
>     CONFIG_OPTS+=("ac_cv_func_inet_ntop=yes")
>     CONFIG_OPTS+=("ac_cv_func_inet_pton=yes")
> fi

Most developers don't use the autoconf stuff and just use the makefile.
config.mak.uname doesn't have NO_INET_NTOP set for SunOS.

If the autoconf scripts or config.mak.uname need fixing, which is
possible, a patch would definitely be welcome.
brian m. carlson (he/him or they/them)
Houston, Texas, US

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 263 bytes --]

  reply	other threads:[~2021-03-28  1:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-28  0:18 Git 2.31.1, Solaris and error: conflicting types for 'inet_ntop' Jeffrey Walton
2021-03-28  0:45 ` brian m. carlson
2021-03-28  1:04   ` Jeffrey Walton
2021-03-28  1:26     ` brian m. carlson [this message]
2021-03-28  7:22       ` Jeff King

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YF/ \ \ \ \

* 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).