Sam Steingold wrote: > > gnulib-tool --import --source-base=src/gllib --m4-base=src/glm4 \ > > --aux-dir=src/build-aux --no-changelog \ > > stdint stdbool ... > > this printed > > gnulib-tool: module config.guess doesn't exist > gnulib-tool: module config.rpath doesn't exist > gnulib-tool: module config.sub doesn't exist > gnulib-tool: module depcomp doesn't exist > gnulib-tool: module install-sh doesn't exist > gnulib-tool: module missing doesn't exist
Oops, this means you tried to pass "config.guess" etc. as module names? Nope, this does not work. The modules are the file names under gnulib/modules/. If you just need to copy some files (such as config.guess, config.sub - these are not part of any module), copy them. 'depcomp', 'install-sh', 'missing' come from "automake --add-missing". > this also printed some suggestions that I followed. > now, configure.in starts with > > AC_CONFIG_SRCDIR(lispbibl.d) > AC_CONFIG_AUX_DIR(build-aux) > AM_INIT_AUTOMAKE > > and has > > AC_CONFIG_FILES([po/Makefile.in gllib/Makefile]) Yes, this looks ok. > and it fails with > > config.status: creating gllib/Makefile > config.status: error: cannot find input file: gllib/Makefile.in > > I hoped that automake would generate gllib/Makefile.in out of > gllib/Makefile.am automatically, but this does not happen (why?) It does not happen because it's simply a different step. You need to invoke (from Makefile.devel) first gnulib-tool, then aclocal, then autoconf, autoheader and automake. > So I had to run "automake gllib/Makefile" by hand. is this right? Yes, right. > do I now commit the generated gllib/Makefile.in to the CVS? According to the clisp CVS policy, yes, you commit it and regenerate it and re-commit it now and then, like you do with other autotools generated files (configure, unixconf.h.in etc.). Bruno
