* Russ Allbery:
>> The correct long-term fix is to change autotools to check a list of
>> well-known paths for more recent versions of the scripts and use them
>> instead of what is provided in the package.
>
> This doesn't regenerate the other files from scratch. This only addresses
> config.{sub,guess}, which is only a small part of the problem.
Is the generated libtool file dependent on the package configuration?
> And if you run autoreconf, that takes care of this update as well
> (at least most of the time). I therefore don't think pursuing this
> is particularly useful, and we should instead make this problem moot
> by using dh-autoreconf or something similar.
Hmm. It's indeed more future-proof. (Most C autoconf tests are
totally invalid C according to any standard published in the last 25
years, currently work by accident, and might fail in the future, so
it's more or less a time bomb.)
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/87vbu4dowd....@mid.deneb.enyo.de
