Documenting tools necessary for GCC [draft]

[Dan Kegel]

Phil Edwards wrote:
>     if <an acinclude.m4 file exists>
>     then
>         <automake is being used; use aclocal(1) to generate aclocal.m4,
>          which will contain acinclude.m4 plus things needed by automake>
>     else
>         <only autoconf is being used; aclocal.m4 is written (not generated)
>          by hand>
>     endif

Thanks!  Then it's just a question of which automake's aclocal to use.
Looks like it's usually automake-1.4
(ftp://ftp.gnu.org/gnu/automake/automake-1.4.tar.gz ?)
but for libstdc++-v3, automake-1.4-p6 is used
(ftp://ftp.gnu.org/gnu/automake/automake-1.4-p6.tar.gz ?):

~/gcc-3.3$ grep 'generated auto' */aclocal.m4
boehm-gc/aclocal.m4:dnl aclocal.m4 generated automatically by aclocal 1.4
fastjar/aclocal.m4:dnl aclocal.m4 generated automatically by aclocal 1.4
libffi/aclocal.m4:dnl aclocal.m4 generated automatically by aclocal 1.4
libjava/aclocal.m4:dnl aclocal.m4 generated automatically by aclocal 1.4
libstdc++-v3/aclocal.m4:dnl aclocal.m4 generated automatically by aclocal 1.4-p6
zlib/aclocal.m4:dnl aclocal.m4 generated automatically by aclocal 1.4


BTW, it looks like the autoconf used to generate gcc-3.3/gcc/configure
was ftp://ftp.gnu.org/gnu/autoconf/autoconf-2.13.tar.gz plus the mawk patch, e.g.
http://pkgcvs.turbolinux.co.jp/centro/index.cgi/~checkout~/autoconf/2.13/Attic/autoconf-2.13-mawk.patch?rev=1.1&content-type=text/plain&hideattic=0
At least, when I used those together and ran autoconf, I got a configure script identical to the one that was shipped.
- Dan