On Tue, Jan 27, 2009 at 07:35:00PM -0600, Perry Smith wrote: > Just to be sure we are on the same page. My directory structure has a > top/src/git-1.6.1 and top/build/git.1.6.1. The src/git-1.6.1 is the > tar ball. The build/git-1.6.1 starts out empty. I cd into it and > then do: ../../src/git-1.6.1/configure <options> After this > completes, you can do "make". I don't see how this would work without automake support, which git does not have. The configure script just generates a config.mak.autogen file, which is included by the Makefile. So you have no Makefile in your build directory. > About 90% of the open source configure / autoconf code out there can > do this with. The other 10% you can not. I like it because when > things die, its easier to grep around the source tree and I blow away > the build directory and start back over and I know that I'm starting > fresh. Another way of solving the same problem: cd untarred-sources git init git add . git commit -m 'pristine sources' Now you can use "git clean" to clean up cruft, not to mention the usual git stuff like tracking any changes you've made and submitting any patches upstream. > I get further. But now test 10 of t0001.sh fails because test_cmp can > not be found. > > Is that a GNU tool? (I didn't see it in git or coreutils.) It's a shell function defined in test-lib.sh (which is sourced by all of the test scripts). -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
