On 2/27/25 18:36, Richard Hansen wrote:
On first glance it appears to be a quoting issue with $HOME/.config.site:
I got a copy of the config.site and confirmed that there are some
under-quoted variable expansions in it. I'm not sure why it didn't fail
before.
Rather than rely on the system
* t/ax/test-defs.in: Set `CONFIG_SITE' to `/dev/null' to prevent the
system's Autoconf site defaults from breaking the test environment.
---
t/ax/test-defs.in | 4
1 file changed, 4 insertions(+)
diff --git a/t/ax/test-defs.in b/t/ax/test-defs.in
index 755445494..9aed4ae10 100644
--- a/t/ax/
On 2/27/25 16:01, Karl Berry wrote:
Or, briefly looking at the logs, I wonder if his incredibly complex
$HOME/config.site file could be interfering with the tests -- though it
never did before. Maybe we somehow have to disable that for automake
test. Hmm.
On first glance it appears to be a quot
On 2/27/25 16:01, Karl Berry wrote:
Hi Richard - a friend (Nelson Beebe) ran the automake test suite on
numerous systems on the 1.17.90 pretest. There was a plethora of
failures, and they seem to related to the new stderr-prefix failure and
shell quoting. Maybe.
Looking. Feel free to revert a
Hi Richard - a friend (Nelson Beebe) ran the automake test suite on
numerous systems on the 1.17.90 pretest. There was a plethora of
failures, and they seem to related to the new stderr-prefix failure and
shell quoting. Maybe.
It seems that the prefixing happened in general? That tap output doesn
