Karl Berry wrote:
> Zack Weinberg wrote:
>> They all appear to be cases of autoconf and/or aclocal
>> getting run when the test suite does not expect them to be run. I am
>> stumped as to why
>
> In short: because the 2.70 autom4te decided not to update configure.
>
> I don't know why not, but I
They all appear to be cases of autoconf and/or aclocal
getting run when the test suite does not expect them to be run. I am
stumped as to why
In short: because the 2.70 autom4te decided not to update configure.
I don't know why not, but I have a guess: maybe the new autom4te ignores
FAIL: t/distcheck-missing-m4.sh
FAIL: t/distcheck-outdated-m4.sh
FAIL: t/libobj-basic.sh
FAIL: t/remake-not-after-make-dist.sh
FAIL: t/vala-non-recursive-setup.sh
Whoops, I see the vala test is the only one you didn't also get,
the rest are duplicates. Sorry for the noise.
The attached patch fixes two of the problems:
Thanks, I pushed that.
There are still four testsuite failures on my dev box,
After applying your patch, running make -j12 check against autoconf 2.70,
I get those failures and several more (as in your case, they don't
appear with 2.69):
FA
