Hi Karl,
On 20/12/23 10:09, Karl Berry wrote:
Could you try running the test on its own?
make VERBOSE=1 check TESTS=t/nodef.sh keep_testdirs=yes
I ran it ten times and it succeeded 70% of the runs, so seems quite
random in line with being due to the timing issue.
Peter
Hi Frederic - (switching to bug-automake for tracking)
https://lists.gnu.org/archive/html/automake/2023-12/msg00034.html
I ran `make check` for this release on Fedora-rawhide and got random
failures. Multiple runs seem to show different failures on all arches
Thanks for the repo
Hi Peter - thanks for trying the automake pretest.
I get one failure (t/nodef)
I suspect a timing problem, since I can't fathom any reason why that
particular test would fail on your system specifically. (The test
basically just runs a minimal automake twice.)
with autoconf 2.71.
Ind
Here's line 8135:
$output =~ s/^((#.*)?\n)*\K/.POSIX:\n\n/;
Ah. I'll get rid of the \K, once I remember/look up what it does :).
(Jacob, if you have any advice, that would be great.)
A simple fix would be for Automake to require Perl 5.10;
Nah, we shouldn't require a jump in
On 2023-12-19 14:54, Karl Berry wrote:
Hi Paul,
help2man: can't get `--help' info from bin/automake
Try `--no-discard-stderr' if option outputs to stderr
So, the obvious question is, why can't help2man run bin/automake?
Clearly it works on other systems, and it doesn't seem like this
Hi Paul,
help2man: can't get `--help' info from bin/automake
Try `--no-discard-stderr' if option outputs to stderr
So, the obvious question is, why can't help2man run bin/automake?
Clearly it works on other systems, and it doesn't seem like this should
be especially system-dependent. Can
