Alexey Mahotkin <alexm(a)hsys.msk.ru> writes:
Humm... Could you describe the nature of the problems? I just
don't understand how it turns out that almost no other program
except XEmacs disables autoconf caching...
XEmacs replaces many of the Autoconf checks with its own versions. It
does not do this out of perversion, but because these checks would not
work for XEmacs as written. Take a look at configure.in, it has a lot
of such examples.
The effect of cache on such mixture between "native" Autoconf and
XEmacs-brewed macros is unknown, and I wouldn't want to test it.
Even outside the context of XEmacs, the cache feature trips you if you
attempt to do anything that was not envisioned by Autoconf authors.
As I said, even in tiny ``Wget'' I had to disable caching of variables
when performing an Autoconf test in a loop. And it was *very*
non-obvious that I had to do this, it took me hours to figure out that
cache was causing the failures.