Hi Bob, On 24 Oct 2011, at 06:34, Bob Friesenhahn wrote: > It seems that there is also a problem if gnulib is not installed on the > machine because 'make check' ends up using a formally-installed gnulib .m4 > file rather than the one in the libtool source tree. I know this because I > don't have gnulib installed on my machine and so 'make check' fails. The > issue is due to an m4 include path problem.
I can't reproduce this. The intent is that bootstrap will clone gnulib into a submodule of your libtool tree, or if you already have a new enough gnulib checkout elsewhere on your machine you can save some bandwidth with: ./bootstrap --gnulib-srcdir=some/gnulib/master/checkout/on/my/machine Are you sure you are starting from a completely clean state? I wonder whether some residue from a pre-gnulib libtool is rearing up out of your autom4te.cache to bite you? Please try the following and let me know if you still have problems: cd your-libtool-git-working-dir git status <save any untracked files you don't want to lose> git clean -f -x -d rm -rf gnulib ./bootstrap This is quite bandwidth intensive since it makes a shallow clone of gnulib over the wire. If you have already cloned it somewhere else on your machine, then go to that directory first and: git checkout master git pull origin master Then back in your libtool working dir, you can use the following bootstrap line instead of the one above: ./bootstrap --gnulib-srcdir=../gnulib (or whatever) Cheers, -- Gary V. Vaughan (gary AT gnu DOT org)
