On Wed, May 02, 2001 at 07:36:30AM +0200, Ralf Corsepius wrote:
> Rick Scott wrote:
> >
> The reason for doing so is config.caches to be considered the number one
> cause of problems for casual installers/users many package maintainers.
> They were sick of having to tell people to run "rm config.cache" first
> :). Not having a config.cache on the toplevel avoids this issue, but
> also prevents being able to pass config.caches down to
> subdir-configure-scripts and shareing config.caches with them.
>
> When explicitly specifying --cache-file=<CACHE_FILE> from the toplevel
> configure script, you should get the old behavior.
>
> BTW: This behavioral change is one of the main reasons why the upcoming
> version of autoconf will be called 2.50 and not 2.15 :).
How do we this ?
We don't have a
cd foo && configure
statement in the script, the call is created by autoconf.
--
Alexander Mai
[EMAIL PROTECTED]
