URL:
<https://savannah.gnu.org/support/?110986>
Summary: "autoconf: forbidden tokens, basic" testsuite
failure on some systems
Group: Autoconf
Submitter: zackw
Submitted: Wed 20 Dec 2023 02:11:14 PM UTC
Priority: 5 - Unprioritized
Severity: 2 - Minor
Status: Need Info
Privacy: Public
Assigned to: None
Originator Email:
Open/Closed: Open
Discussion Lock: Any
Operating System: None
_______________________________________________________
Follow-up Comments:
-------------------------------------------------------
Date: Wed 20 Dec 2023 02:11:14 PM UTC By: Zack Weinberg <zackw>
Observed by me on at least x86_64-netbsd9 and sparc64-solaris10: the
"autoconf: forbidden tokens, basic" test fails because the second invocation
of autoconf prints the same "possibly undefined token" error messages as the
first invocation, contrary to the test's expectations. This is probably more
fallout from the sub-second timestamp changes: the second invocation is
supposed to pull 'configure' from cache and not re-run M4. Unfortunately, the
second invocation of autoconf clobbers the mtime of all the files involved,
making it difficult to figure out exactly what went wrong after the fact.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/support/?110986>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
