[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

autoreconf vs AC_CONFIG_SUBDIRS

From: Ralf Corsepius
Subject: autoreconf vs AC_CONFIG_SUBDIRS
Date: 07 Nov 2001 11:45:41 +0100


Autoconf and it's documentation explictly state that AC_CONFIG_SUBDIRS
are treated as optional directories and are not required to be present
in a source-tree.

     If a given DIR is not found, no error is reported, so a
     `configure' script can configure whichever parts of a large source
     tree are present. 

However, autoreconf seems to require all directories specified as
AC_CONFIG_SUBDIRS to be present in a source-tree.

# cat configure.ac
# autoreconf -i -f -v 
autoreconf: working in `.'
autoreconf: configure.ac: not using Gettext
autoreconf: running: libtoolize --copy --force
You should update your `aclocal.m4' by running aclocal.
autoreconf: running: aclocal -I m4 --output=aclocal.m4t
autoreconf: `aclocal.m4' is unchanged
autoreconf: running: automake --add-missing --copy --force-missing
Makefile.am:9: required directory ./libpath does not exist
autoreconf: automake failed with exit status: 1
 at /opt/dev/bin/autoreconf line 348

IMHO, autoreconf's behavior doesn't match with autoconf's behavior, and
therefore should be changed, i.e. I am in favor of letting autoreconf
either ignore or just warn about AC_CONFIG_SUBDIRS which are not present
in a source-tree, but not to abort.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]