On Dec 4, 2007 10:35 AM, Hongliang Wang <[EMAIL PROTECTED]> wrote: > Here is the my autogen.sh > ================================================== > #!/bin/sh > # Run this to generate all the initial makefiles, etc. [snip] > for dir in . > do > echo processing $dir > (cd $dir; \ > aclocalinclude="$ACLOCAL_FLAGS"; \ > aclocal $aclocalinclude; \ > autoheader; automake --add-missing --gnu $am_opt; autoconf) > done
Why don't you just use autoreconf - which does exactly what autogen.sh does, just better? From the automake manual: Many packages come with a script called `bootstrap.sh' or `autogen.sh', that will just call `aclocal', `libtoolize', `gettextize' or `autopoint', `autoconf', `autoheader', and `automake' in the right order. Actually this is precisely what `autoreconf' can do for you. If your package has such a `bootstrap.sh' or `autogen.sh' script, consider using `autoreconf'. That should simplify its logic a lot (less things to maintain, yum!), it's even likely you will not need the script anymore, and more to the point you will not call `aclocal' directly anymore. (Node: Future of aclocal)
