Hi, thanks again for your quick and helpful reply. On Wed, Mar 3, 2010 at 7:33 AM, Ralf Wildenhues <Ralf.Wildenhues@xxxxxx> wrote: > * Steffen Dettmer wrote on Tue, Mar 02, 2010 at 04:25:50PM CET: >> For new subdirectories with new Makefile.am autoconf/automake >> fails because Makefile.in seems not to be created automatically, > > I'm not sure I understand. The normal way to add a new directory is to > add > AC_CONFIG_FILES([dir/Makefile]) (or add to AC_OUTPUT, seems with AC_OUTPUT, AC_CONFIG_FILES won't work) > to configure.ac, write dir/Makefile.am, and add something like > SUBDIRS += dir > > to a Makefile.am above dir (or sub/../dir if more than one level above). > Then, unless you have maintainer-mode turned off, just run 'make'.[1] ohh, indeed. It seems I tested wrongly and that I had a different problem. Seems I missed an important warning in the heaps of warning I got :( WARNING: `aclocal-1.11' is missing on your system.... which seems to be caused because I tried to use automake without `make install' it, which seems not to be allowed. Sorry for the inconvenience. It just works correctly. Great! So if we would make the upgrade we could drop workarounds, good :) >> 2) new autoconf directories: > > I'd like to understand your use case in (1) first. I retested this as well but still don't see it working. So probably I made another mistake :) I have a new dir with dir/configure.in and added it to ./configure.in's AC_CONFIG_SUBDIRS([dir]). In Makefile.am I have SUBDIRS=@subdirs@ admin make then runs aclocal, automake, autoconf and ./config.status --recheck, but only in `.' not in `dir'. Then it recurses SUBDIRS, finally dir and aborts: make[1]: *** No rule to make target `all'. Stop. in `dir' there is no configure and no Makefile. oki, Steffen _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf
