[sr #110397] autoconf 2.70: autotest.m4 error

Follow-up Comment #6, sr #110397 (project autoconf): Without patch, outside of homebrew, installing automake 1.16.3 with autoconf 2.70 fails: rmeur /tmp/autoconf-2.70 $ ./configure --prefix=/tmp checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is

[sr #110397] autoconf 2.70: autotest.m4 error

Follow-up Comment #5, sr #110397 (project autoconf): Yes, of course. That makes sense. I'll need to look into finding you a machine for remote shell access. However, the build scripts for automake and autoconf are very simple. For automake, it (essentially) runs these commands in the build

autoconf-2.70 increases make check failure of automake on Solaris x86/x64

Hello, Installed autoconf-2.70, and found it increases make check failure of automake. $ uname -a SunOS hidden 5.11 11.3 i86pc i386 i86pc $ gcc --version gcc (GCC) 10.2.0 $ autoconf --version autoconf (GNU Autoconf) 2.70 In automake-1.16.3 directory, $ ./configure CC=gcc $ make $ make check

[sr #110397] autoconf 2.70: autotest.m4 error

Follow-up Comment #4, sr #110397 (project autoconf): The aclocal command is part of automake; you need existing installed copies of both autoconf and automake to run autoreconf -iv on either autoconf or automake. It's kinda the same thing as needing a C compiler already before you can build gcc.

[sr #110397] autoconf 2.70: autotest.m4 error

Follow-up Comment #3, sr #110397 (project autoconf): Sorry, I just noticed you mentioning the automake configure script needing to be regenerated with the new autoconf. That's not done in the CI run, which just calls the configure script immediately. I just tried to run it locally instead:

[sr #110397] autoconf 2.70: autotest.m4 error

Follow-up Comment #2, sr #110397 (project autoconf): Thanks for the quick response. Here are the autoconf and automake logs from the CI node running macOS 11: https://www.dropbox.com/s/ts1nx36buk3x7a8/logs.tar.gz?dl=1 The logs look similar on the nodes running 10.14 and 10.15, but let me know if

[sr #110397] autoconf 2.70: autotest.m4 error

Update of sr #110397 (project autoconf): Status:None => Need Info ___ Follow-up Comment #1: Thanks for the bug report. It looks like the smoke-test code in your Homebrew recipe was

[sr #110397] autoconf 2.70: autotest.m4 error

URL: Summary: autoconf 2.70: autotest.m4 error Project: Autoconf Submitted by: None Submitted on: Tue 08 Dec 2020 11:09:23 PM UTC Category: None Priority: 5 -

Re: autoconf-2.70 released [stable]

Woohoo!! About time! :) On Tue, Dec 8, 2020 at 12:14 PM Zack Weinberg wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > We are pleased to announce stable release 2.70 of GNU Autoconf. > > This release includes eight years of development work since the > previous release, 2.69.

[sr #110396] autoconf 2.70 c99 check uses ac_c_conftest_c89_program

URL: Summary: autoconf 2.70 c99 check uses ac_c_conftest_c89_program Project: Autoconf Submitted by: None Submitted on: Tue 08 Dec 2020 09:12:34 PM UTC Category: None

[sr #109513] Release Autoconf 2.70

Update of sr #109513 (project autoconf): Status: In Progress => Done Open/Closed:Open => Closed ___ Follow-up Comment #4: Autoconf 2.70 was

autoconf-2.70 released [stable]

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 We are pleased to announce stable release 2.70 of GNU Autoconf. This release includes eight years of development work since the previous release, 2.69. Noteworthy changes include support for the 2011 revisions of the C and C++ standards, support

Re: autoreconf --install --force broke on files with no timestamps

On Tue, Dec 8, 2020 at 7:09 AM Pascal Terjan wrote: > > http://git.savannah.gnu.org/gitweb/?p=autoconf.git;a=commit;h=40fa9edce6ad1a05988e4743a7ca64c3a8b3208d > broke many things as it is no longer possible to use autoreconf > --force --install to replace a file with no timestamp. > > A lot of

autoreconf --install --force broke on files with no timestamps

http://git.savannah.gnu.org/gitweb/?p=autoconf.git;a=commit;h=40fa9edce6ad1a05988e4743a7ca64c3a8b3208d broke many things as it is no longer possible to use autoreconf --force --install to replace a file with no timestamp. A lot of install-sh files do not have one. A few examples: