Re: regex.m4 test too strict?

[Sam Steingold]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Sam Steingold wrote:
> it appears that gnulib regex.m4 declares my regex broken:
> 
> config.cache:818:gl_cv_func_re_compile_pattern_working=${gl_cv_func_re_compile_pattern_working=no}
> 
> this is weird given that the system is an fc5 (glibc 2.4).
> are your sure glibc 2.4 has a broken regex implementation?

apparently this is because the system is 64-bit, which still seems wrong
because this is a glibc system and should be using the exact same code.

incidentally, why isn't ac_use_included_regex cached?
this is not a vain question because I want to use it to pass the results
of the check from the top-level configure to the module subconfigure.
I cannot use gl_cv_func_re_compile_pattern_working instead because it
can be overriden by with_included_regex.
Thus, unless ac_use_included_regex is cached, I will have to duplicate
the gl_cv_func_re_compile_pattern_working/with_included_regex logic.

Is there any chance that ac_use_included_regex will be renamed to
ac_cv_use_included_regex and cached?

Thanks.
Sam.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHKL1gPp1Qsf2qnMcRAn7HAKCwhpE4ljsrVyUOwkJYciURYYsNVACdFr6Y
gsBpNfOZokOryyIoDAQ5JVQ=
=F98S
-----END PGP SIGNATURE-----