On 06/16/2011 12:12 AM, Bruno Haible wrote:
I wrote:
Please review and comment. I'll wait for objections for a week.
The week is over. I have now pushed the series of patches, after doing an
additional test with --create-megatestdir.
Something went wrong because a bootstrap with all modules is now broken.
These modules contain references to a deleted m4 file:
crypto/gc-arcfour:m4/arcfour.m4
crypto/gc-des:m4/des.m4
crypto/gc-hmac-md5:m4/hmac-md5.m4
crypto/gc-hmac-sha1:m4/hmac-sha1.m4
crypto/gc-rijndael:m4/rijndael.m4
It causes the bootstrap (--create-testdir --with-tests --dir=foo) to fail:
/home/tgc/projects/gnulib/gnulib/gnulib-tool: *** file
/home/tgc/projects/gnulib/gnulib/m4/arcfour.m4 not found
Removing those references is not enough since the macros from those
deleted m4 files are also still called:
m4/gc-arcfour.m4:gl_ARCFOUR
m4/gc-des.m4:gl_DES
m4/gc-hmac-md5:gl_HMAC_MD5
m4/gc-hmac-sha1:gl_HMAC_SHA1
m4/gc-rijndael:gl_RIJNDAEL
Which causes this error:
configure:35438: error: possibly undefined macro: gl_ARCFOUR
If this token and others are legitimate, please use m4_pattern_allow.
See the Autoconf documentation.
configure:35502: error: possibly undefined macro: gl_DES
configure:35520: error: possibly undefined macro: gl_HMAC_MD5
configure:35541: error: possibly undefined macro: gl_HMAC_SHA1
configure:35769: error: possibly undefined macro: gl_RIJNDAEL
-tgc