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
