On Wed, 2009-03-11 at 07:16 -0400, Mike Frysinger wrote: > On Wednesday 11 March 2009 06:46:13 Alan Jenkins wrote: > > 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. Ah, I get it. Clearly I shouldn't do this at the end of the day. But isn't there another way to get that directory automatically included? > > 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". Indeed. I find in life that I cannot use something I don't understand completely. In this case I knew what was wrong but not why you hadn't hit it - now I see what autoreconf does. I still won't use it, but it's nice to know how it would have done this for me. > but i'm pretty sure aclocal itself wont pull it out. I'll look at the docs later and see if there's a way to make it use m4/. On the subject of files, I had made the "HACKING" file as a kind of "I just want to do something, give me the minimum information" source. But maybe that's just too lazy and there should only be a README. Jon. -- To unsubscribe from this list: send the line "unsubscribe linux-modules" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
