Re: [GNU Autoconf 2.71] testsuite: 10 11 12 14 37 92 236 238 239 240 293 299 397 430 431 432 433 434 435 436 437 438 439 440 509 514 failed

Bob Harris <[email protected]>
Newsgroups gmane.comp.sysutils.autoconf.bugs
Message-ID <[email protected]>
On Apr 25, 2022, at 12:07 PM, Zack Weinberg <[email protected] <mailto:[email protected]>> wrote:
> I *think* this is the same problem as https://savannah.gnu.org/support/?110492 <https://savannah.gnu.org/support/?110492> : current Autoconf doesn't work correctly with the (rather old) version of GNU M4 that ships with MacOS. Please try installing a current version of GNU M4 in your PATH and then retry the build and testsuite.

Synopsis:
That cleared up all but two of the failed tests. 509 and 514 still report FAILED.

I’m not sure whether I should submit that as a new problem, or if this thread will (eventually) try to resolve it.

Detail:
I installed m4 version 1.4.19, then did “make uninstall” for autoconf, deleted the autoconf-2.71 tree, and copied autoconf-2.71 fresh from the tarball.

Then I did
	./configure —prefix=something
	make
	make check

Comparing log files from my previous install attempt (when I have the apple version of m4) with this one, I notice that configure had reported a warning about m4 that the new install attempt did not ("WARNING: the version of M4 that was found does not support -g”).

“make check” takes nearly a half hour. So doing a binary search over different versions of m4 would take a while. My hypothesis is that I can just look for that warning from configure until I zero in on the version that makes that disappear, then try make and make check with that version.

Still, though, I need to resolve the failures of 509 and 514 before I proceed.

I didn’t see any easy way to search the same bug database (that had https://savannah.gnu.org/support/?110492 <https://savannah.gnu.org/support/?110492>) to see if I could find info about 509 and 514.

Thanks,
Bob H
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.