Re: autoconf 2.49c AC_CACHE_CHECK failure

[Akim Demaille]

| Hi,

Salut Nicolas!

| I just tried CVS autoconf on Tru64 unix v5.1 computer and noticed a
| failure of AC_CACHE_CHECK if an autoconf site file exists in default
| prefix location `/usr/local'. without this `config.site' defaults file
| all tests are successful.
| 
| address@hidden [~]> cat /usr/local/share/config.site 
| ## Autoconf default configuration file

Arg, never thought about this issue.  Thanks!  Actually I'm surprised
this is the only feature.

I'd like to have the opinion of other people on this issue:

| ========================================
| Testing suite log for GNU Autoconf 2.49d
| ========================================
| 
| Failed tests:
|   23: base.at:205     AC_CACHE_CHECK
| 
| Skipped tests:
|  148: foreign.at:9    Autoconf & Libtool
| 
| ## ---------- ##
| ## Platform.  ##
| ## ---------- ##
| 
| hostname = medusa.sis.pasteur.fr
| uname -m = alpha
| uname -r = V5.1
| uname -s = OSF1
| uname -v = 732
| 
| /usr/bin/uname -p = alpha
| /bin/uname -X     = unknown
| 
| /bin/arch              = unknown
| /usr/bin/arch -k       = unknown
| /usr/convex/getsysinfo = unknown
| hostinfo               = unknown
| /bin/machine           = alpha
| /usr/bin/oslevel       = unknown
| /bin/universe          = unknown
| 
| PATH = 
/home/njoly/temp/autoconf/tests:/home/njoly/temp/autoconf:/home/njoly/bin:/local/bin:/local/sbin:/local/teTeX/bin/alphaev56-dec-osf5.0:/gensoft/bin:/sbin:/usr/sbin:/usr/bin:/usr/bin:/usr/bin/X11
| 
| ====================================
| Testing suite for GNU Autoconf 2.49d
| ====================================
| 23. ./base.at:205: testing AC_CACHE_CHECK...
| ./base.at:212: autoconf --autoconf-dir .. -l $at_srcdir 
| ./base.at:213: ./configure -q
| 0a1
| > loading site script /usr/local/share/config.site
| 23. ./base.at:205: FAILED near `base.at:213'

This is the only failure because that's the only place were we
actually check configure's stdout.

Should we (i) make sure not to use config.site in the test suite, or
(ii) have this test grep out this message?

It sounds good to have the test suite protected from the user, but
OTOH, it sounds good to have a means to check configures using the end
user's config.site.