On Thu, Feb 26, 2009 at 10:23:54AM -0500, Tim Visher wrote: > The reason I'm using `configure` at all is that when I simply do a > `make` without a `make configure; ./configure` first, it fails with a > message like: > > $ make > CC fast-import.o > In file included from builtin.h:4, > from fast-import.c:142: > git-compat-util.h:100:19: iconv.h: No such file or directory > make: *** [fast-import.o] Error 1 > > Once I configure, even without any options, it builds fine and I can It sounds like you don't have iconv. You can build with: make NO_ICONV=1 on such a platform, which is more or less what the configure script is doing. Try running './configure' and investigating the config.mak.autogen it generates; this gets pulled directly into the Makefile. You can correlate the variables it is setting with the descriptions in the Makefile. > My eventual goal is to have git installed with man, info, and html > pages, into my (and my fellow developers') personal bin, man, info, > and html directories at ~/x. It appeared that I could do that with > ./configure but per the response I got earlier, this doesn't seem to > be the case. I think the right thing to do is to fix the broken autoconf support, as per my other message. But you can workaround it with: ./configure make htmldir=~/man bindir=~/bin mandir=~/man infodir=~/info The latter command is simply overriding what's in the Makefile with what you provide on the command line (so any defaults, or anything provided by ./configure is ignored). -Peff -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
