Hello,
When building http://ftp.gnu.org/gnu/autoconf/autoconf-2.69.tar.xz
using Bash 5.0, make check reports many failures concerning the
following Bash 5.0's change of behavior, quoting
https://lists.gnu.org/archive/html/bug-bash/2019-01/msg00063.html:
There are a few incompatible changes betwee
Hello,
On Thu, Feb 20, 2020 at 9:55 PM Zack Weinberg wrote:
>
> On Thu, Feb 20, 2020 at 3:44 PM Tadeus Prastowo <0x66726...@gmail.com> wrote:
> >
> > When building http://ftp.gnu.org/gnu/autoconf/autoconf-2.69.tar.xz
> > using Bash 5.0, make check reports many
Hi Paul,
I found that at the commit immediately preceding 2ca0d57, building
automake-1.16.1 can successfully run the tests t/autohdr4.sh and
t/autohdr-subdir-pr12495.sh.
I cannot build commit 2ca0d57. It fails with:
autom4te_perllibdir='.'/lib AUTOM4TE_CFG='lib/autom4te.cfg'
./bin/autom4te -B '.
On Mon, Feb 24, 2020 at 10:07 PM Paul Eggert wrote:
>
> On 2/24/20 12:23 PM, Tadeus Prastowo wrote:
> > My question is: should the problem be fixed in autoconf by fixing
> > whatever goes wrong with commit 2ca0d57? Or, should the problem be
> > fixed in automake?
>
Hi,
Could someone try to checkout the Autoconf git repository at commit
2ca0d57 (https://git.savannah.gnu.org/cgit/autoconf.git/commit/?id=2ca0d57)
and build it, please?
I would like to know whether it is possible at all to build commit
2ca0d57 out of the box or the commit is indeed committed in
On Thu, Feb 27, 2020 at 7:33 PM Zack Weinberg wrote:
>
> On Thu, Feb 27, 2020 at 12:40 PM Tadeus Prastowo <0x66726...@gmail.com> wrote:
> > Could someone try to checkout the Autoconf git repository at commit
> > 2ca0d57 (https://git.savannah.gnu.org/cgit/autoconf.git/com
