[autoconf-conversion] Something to start with
Daniel Jacobowitz
drow at false.org
Sat Jun 14 21:25:35 UTC 2003
On Sat, Jun 14, 2003 at 05:20:41PM -0400, DJ Delorie wrote:
>
> > [I am a little worried. I ran into what looks like a cache
> > incompatibility; I configured libiberty using 2.50, backed down to the
> > 2.13 configure script, did it again, and got quoting errors in
> > config.cache. But I can't reproduce it now, so I'm only a little
> > worried.]
>
> Yup, we know about that. 2.50 might not be usable; we might need some
> other 2.5x that's fixed the cache bug. Or we might need to disable
> the cache for the interim.
Er, I'm slipping. Debian for hysterical reasons (really) labels modern
autoconf as "2.50". It's actually 2.57.
I wouldn't object to disabling the cache for the interim if we had a
bit more momentum than we do now. I say let's leave it alone unless it
bites again.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
More information about the autoconf-conversion
mailing list