From: Jeff King <peff@peff.net>
To: Jeffrey Walton <noloader@gmail.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: git-compat-util.h:798:13: error: conflicting types for ‘inet_ntop’
Date: Mon, 3 Feb 2020 05:01:08 -0500 [thread overview]
Message-ID: <20200203100108.GA1072975@coredump.intra.peff.net> (raw)
In-Reply-To: <CAH8yC8=_9OtBJ2dMJPSGb3bYf-b+C6GYXx+NP4Dy_LDCoiks+A@mail.gmail.com>
On Mon, Feb 03, 2020 at 03:59:19AM -0500, Jeffrey Walton wrote:
> > :) I second Junio's notion there that you may be better off skipping
> > ./configure entirely.Thanks Jeff.
>
> I run 'make configure' and configure because that's what the INSTALL
> tells me to do.
>
> Forgive my ignorance... If I don't run configure, then how do I
> configure things?
Above the "Alternatively you can use autoconf..." in INSTALL, there is:
The beginning of the Makefile documents many variables that affect the
way git is built. You can override them either from the command line,
or in a config.mak file.
You often don't need to set most of those flags, because
config.mak.uname picks some defaults based on the platform we find via
"uname".
So I'd first just try "make" without any config. If that doesn't work
out of the box, a patch to update config.mak.uname would be welcome.
If "./configure && make" also doesn't work, certainly patches are
welcome there, too. The reason I say you may be better off skipping it
is that historically it seems to not be kept as up-to-date. Usually it
would not make things _worse_ to run it, but in this inet_ntop case, I
think it does.
-Peff
next prev parent reply other threads:[~2020-02-03 10:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-01 11:39 git-compat-util.h:798:13: error: conflicting types for ‘inet_ntop’ Jeffrey Walton
2020-02-01 12:12 ` 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 [this message]
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:
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=20200203100108.GA1072975@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=noloader@gmail.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).