RE: autoconf 2.50 tests and cache

[Tim Van Holder]

> Tim> Yes, but some platforms (like DJGPP) are not yet 100% supported
> Tim> directly - we need config.site to make path seraching work.
> 
> :(
> 
> I don't remember what remains to be done for DJGPP.

Not a lot really.  There's probably a few places (AS_DIRNAME comes to
mind) where support for both / and \ as pathseps needs to be added.
config.site is currently still needed to help test -f out.  With stock
autoconf, config.site needs to set TEST_FINDS_EXE, so test -f foo will
find foo.exe/foo.bat/... as well (kind of like our test -x always does).
With my local patched version (using $ac_executable_extensions), the
list of know executable extensions needs to be set in config.site.
This could/should move to autoconf proper, but I don't see how we can
test for this without testing for the platform.
And there's a few other tweaks: the loop in config.status needs
DJGPP-specific changes to prevent problems due to ':' being both a
drivesep and a file:template separator (I'm not sure we can integrate
this cleanly into stock autoconf, and changing the file:template sep is
probably unacceptable), and there's still my old patch to properly handle
quoted args when configuring in subdirs.
I'll try to get a full set of patches together soon, but I'm pretty busy
at the moment.

> Tim> Explicitly setting CONFIG_SITE to the empty string should ensure
> Tim> the same config.site is loaded during the entire testsuite, so
> Tim> that should be enough.
> 
> Sorry, I don't get it here.

I mean that as long as the entire testsuite uses the same values, things
should be OK; clearing out $CONFIG_SITE would prevent the user from
setting it for some tests and unsetting it for others.  It doesn't
prevent him/her from modifying the system-wide config.site, but that
probably happens less often.