This is the mail archive of the
mailing list for the GDB project.
Re: Why autoconf 2.13?
> DJ Delorie <firstname.lastname@example.org> writes:
> |> > What's wrong with "rm config.cache"? autoconf 2.50+ does not even create
> |> > a config.cache by default any more.
> |> |> The problem is when someone does "cvs update" and suddenly everything
> |> breaks because they got a newly configured configure which doesn't
> |> like the config.cache they've got sitting around.
> I still regard it as an acceptable workaround, since the data in it can
> become stale quite easily anyway, just by changing anything in the build
Yes. If an update contains autoconf changes, I always end up rebuilding