On Wednesday 11 March 2009 06:46:13 Alan Jenkins wrote: > Mike Frysinger wrote: > > On Wednesday 11 March 2009 02:26:57 Jon Masters wrote: > >> On Mon, 2009-03-09 at 21:35 +0000, Alan Jenkins wrote: > >>> 1. Move autoconf extensions to m4 directory, as suggested by Mike > >>> Frysinger. > >> > >> I'm sleeping now but perhaps you'll take a look at the tree and send me > >> a patch so that configure can see AX_ENABLE_BUILDDIR, which it isn't > >> right now on a clean build: > >> > >> checking build system type... i686-pc-linux-gnu > >> checking host system type... i686-pc-linux-gnu > >> checking target system type... i686-pc-linux-gnu > >> ./configure: line 1966: syntax error near unexpected token `build' > >> ./configure: line 1966: `AX_ENABLE_BUILDDIR(build)' > >> > >> Apologies that I didn't check this bit properly before committing - I'll > >> clean it up in the morning either way :) > > > > how did you run autotools ? if you ran like `aclocal` manually rather > > than `autoreconf`, then you'd see this error. > > I did wonder how the bootstrap process works; I didn't find it in the > autotools docs. So it's more complicated than the "full" command > sequence in the README. HACKING has the same sequence as well, which > won't work anymore. > > I take Jon's point, it's dangerous to treat autotools as > incomprehensible magic. So I think we should keep the full command > sequence documented, but change it to use "aclocal -I m4". the autotools in README and HACKING should be merged. easiest might be for bullet 6) in the README to say "see the HACKING file". and then in the HACKING file, suggest people start with `autoreconf -i`, or fall back to the full sequence (including adding -Im4 to aclocal). the AMFLAGS in Makefile.am is used by autoreconf and such, but i'm pretty sure aclocal itself wont pull it out. -mike
Attachment:
signature.asc
Description: This is a digitally signed message part.
