archive mirror
 help / color / mirror / Atom feed
From: Jeffrey Walton <>
To: Git List <>
Subject: git-compat-util.h:798:13: error: conflicting types for ‘inet_ntop’
Date: Sat, 1 Feb 2020 06:39:24 -0500	[thread overview]
Message-ID: <> (raw)

Hi Everyone,

I'm building the 2.25 release tarball on Solaris 11.3 i86pc. I'm
catching an error:

$ gmake
    CC fuzz-commit-graph.o
In file included from commit-graph.h:4:0,
                 from fuzz-commit-graph.c:1:
git-compat-util.h:798:13: error: conflicting types for ‘inet_ntop’
 const char *inet_ntop(int af, const void *src, char *dst, size_t size);
In file included from git-compat-util.h:226:0,
                 from commit-graph.h:4,
                 from fuzz-commit-graph.c:1:
/usr/include/arpa/inet.h:43:20: note: previous declaration of
‘inet_ntop’ was here
 extern const char *inet_ntop(int, const void *_RESTRICT_KYWD,
gmake: *** [fuzz-commit-graph.o] Error 1


$ cat -n /usr/include/arpa/inet.h
    41  #if !defined(_XPG4_2) || defined(_XPG6) || defined(__EXTENSIONS__)
    42  extern int inet_pton(int, const char *_RESTRICT_KYWD, void
    43  extern const char *inet_ntop(int, const void *_RESTRICT_KYWD,
    44                          char *_RESTRICT_KYWD, socklen_t);
    45  #endif /* !defined(_XPG4_2) || defined(_XPG6) ||
defined(__EXTENSIONS__) */


             reply	other threads:[~2020-02-01 11:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-01 11:39 Jeffrey Walton [this message]
2020-02-01 12:12 ` git-compat-util.h:798:13: error: conflicting types for ‘inet_ntop’ Jeffrey Walton
2020-02-01 12:34   ` Jeffrey Walton
2020-02-03  8:54   ` Jeff King
2020-02-03  8:59     ` Jeffrey Walton
2020-02-03 10:01       ` Jeff King
2020-02-03 10:46     ` Jeffrey Walton
2020-02-03 11:02       ` 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 \ \ \ \

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