MB> autoconf-2.50 is a major change from 2.13. Upgrading _properly_ will MB> be a lot of work. In particular, a lot of the redefinitions in MB> configure.in are to change the behavior of configure in a way that's no MB> longer necessary in the new autoconf. New macros introduced in MB> autoconf 2.50 should also be used. Are there any plans to turn on back caching in configure.in? Maybe it's adequate to turn caching back on by default in beta and try to shake out "surprises" that'll appear? It's sometimes very annoying without cache... --alexm