bug#13514: [PATCH v2 0/0] AC_CONFIG_MACRO_DIR && non-existent directory

On 02/11/2013 01:11 PM, Pavel Raiskup wrote: > Hi, thanks for your comments! > Thanks for your patches, and you patience. > Here is second iteration of my proposal. > > [PATCH 1/2] aclocal: just warn if the primary local m4 dir doesn't > aclocal.in | 10 ++ > t/aclocal-macrod

bug#13514: [PATCH v2 0/0] AC_CONFIG_MACRO_DIR && non-existent directory

Hi, thanks for your comments! Here is second iteration of my proposal. [PATCH 1/2] aclocal: just warn if the primary local m4 dir doesn't aclocal.in | 10 ++ t/aclocal-macrodir.tap | 22 +- [PATCH 2/2] aclocal: fix for more-than-once specified directories

bug#13514: [PATCH 2/2] aclocal: fix for more-than-once specified directories

Related to automake bug#13514. Do not explore these directories multiple times in 'aclocal'. This causes problems on older packages that specify configure.ac: AC_CONFIG_MACRO_DIRS([m4]) Makefile.am: ACLOCAL_AMFLAGS = -I m4 when the m4 directory does not exist. See:

bug#13514: [PATCH 1/2] aclocal: just warn if the primary local m4 dir doesn't exist (no error)

Related to automake bug#13514. Every bootstrapping process which does not need to have the local macro directory existing in version control system (because it does not have any user-defined macros) would fail during 'autoreconf -vfi' phase if the AC_CONFIG_MACRO_DIRS([m4]) is specified (to force