Ben Pfaff wrote: > Michael Biebl <[email protected]> writes: > >> I followed the advise from libtoolize and added >> `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and >> `-I m4' to ACLOCAL_AMFLAGS in Makefile.am >> >> When I now run "autoreconf -vfi" from a fresh git checkout, where the >> (empty) m4/ directory does not yet exist, I get a failure: >> >> autoreconf -vfi >> autoreconf: Entering directory `.' >> autoreconf: configure.ac: not using Gettext >> autoreconf: running: aclocal --force -I m4 >> aclocal: couldn't open directory `m4': No such file or directory >> autoreconf: aclocal failed with exit status: 1 >> >> I suggest that either autoreconf or aclocal should create that >> directory, before any of the tools tries to copy it's macro files there. > > Hi Michael.
Hi Ben > It's hard for me to see exactly why any of the tools should > create this directory. libtoolize already does it that way. It seems to me that, if you want files to > be put in a particular source directory, it's reasonable for the > tools to assume that you have already created that directory. > > Can you explain why you think this is a bug? Principle of least surprise. If the tools can create the directory itself and not fail, why should they not do it? It would also be consistent with what libtoolize is already doing. Third, and this is more a limitation of Git, you can't put empty directories in Git (unless you resort to imho ugly workarounds like putting empty . files in a m4/ directory). So it is up to everyone checking out a Git repository, to create the m4/ on their own. That is imo just inconvenient. People seeing that error message probably don't immediately know, what that error message means and can easily be solved by simply creating a m4/ directory. Cheers, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
