diff options
author | 2025-02-27 01:52:35 -0500 | |
---|---|---|
committer | 2025-02-27 02:02:30 -0500 | |
commit | 7b8499943ab93e837b92eceaf8b85e5646327b7f (patch) | |
tree | 9697c4aec686cf427f42e44c919c72b4a3b50770 /perl-core/CPAN | |
parent | dev-python/python-tests: Stabilize 3.13.2 hppa, #950064 (diff) | |
download | gentoo-master.tar.gz gentoo-master.tar.bz2 gentoo-master.zip |
We apply patches to Makefile.am, so we must run eautomake (but running
all of eautoreconf isn't necessary). Successfully doing so requires
knowing exactly which version of automake to use, which works great as
it is slotted, except we did not in fact actually specify it.
In theory, autotools.eclass detects mismatches and forces a full
eautoreconf. This is broken in two ways:
- I had originally optimistically set WANT_AUTOCONF=none, so we might
not have what we need in such a case
- the logic is actually broken, entwined with the effects of a commit
from 2009 in gentoo-historical-2.git: 773f4f230b88ffbcc9de281f83dbd1c905965564
This wiped out WANT_AUTOMAKE= when checking the installed version due
to ??? (it was 2009 so who knows whether it was always broken or is
simply incompatible with later changes any time in the next 16 years)
and causes automake to "see" a different version for comparison than
the one that actually runs. The eclass is clearly broken *today*
either way, and investigation is ongoing as to how to fix it, but this
is a moot point for the purpose of sys-devel/patch...
I originally didn't notice this as Patch was created with automake 1.16,
which was also the latest version stable in Gentoo. Well erm, sort of.
1.17 was stabled barely a day ago and I simply hadn't gotten upgraded to
it yet. Oops. "configure.ac:33: error: version mismatch."
Forcing the correct slotted automake solves all (okay fine, *most* of)
our problems.
Signed-off-by: Eli Schwartz <eschwartz@gentoo.org>
Diffstat (limited to 'perl-core/CPAN')
0 files changed, 0 insertions, 0 deletions