Eric Blake wrote:
> I've run into problems most frequently with two types of related
> changes:
There's also a problem when the set of macros defined in .m4 files changes.
Then 'autoconf' complains.
How to reproduce:
$ ./gnulib-tool --create-testdir --dir=/tmp/testdir wchar
$ cd /tmp/testdir
$ configure
$ make
$ gnulib-tool --source-base=gllib --m4-base=glm4 --add-import iswblank
$ make
$ gnulib-tool --source-base=gllib --m4-base=glm4 --remove-import iswblank
$ make
CDPATH="${ZSH_VERSION+.}:" && cd . && /bin/sh /tmp/testdir/build-aux/missing
--run aclocal-1.11 -I glm4
cd . && /bin/sh /tmp/testdir/build-aux/missing --run automake-1.11 --foreign
CDPATH="${ZSH_VERSION+.}:" && cd . && /bin/sh /tmp/testdir/build-aux/missing
--run autoconf
configure:4572: error: possibly undefined macro: gl_NEXT_HEADERS
If this token and others are legitimate, please use m4_pattern_allow.
See the Autoconf documentation.
configure:4580: error: possibly undefined macro: gl_CHECK_NEXT_HEADERS
configure:4598: error: possibly undefined macro: gl_WARN_ON_USE_PREPARE
make: *** [configure] Error 1
Bruno
--
In memoriam Karim Mohammedzadeh
<http://en.wikipedia.org/wiki/Karim_Mohammedzadeh>
