bug#16714: make check failures

2022-01-22 Thread Karl Berry
ACLOCAL=aclocal make check I guess our internal make check initialization should unset ACLOCAL if it's set? Maybe with a warning, since it might be expected. Is something more needed? --thanks, karl.

bug#16714: make check failures

2022-01-17 Thread Mike Frysinger
retitle 16714 make check failures when ACLOCAL=aclocal is in environment tag 16714 = confirmed thankyou looks like your redundant $ACLOCAL in the environment is breaking things. there should be no reason to have that: ACLOCAL=aclocal -I /usr/share/aclocal that said, we shouldn't be blowing up w

bug#16714: make check failures

2014-04-21 Thread Rachel Mant
On 21/04/14 14:44, Stefano Lattarini wrote: On 04/21/2014 11:43 AM, Rachel Mant wrote: On 21/04/14 11:21, Stefano Lattarini wrote: tags 16714 + moreinfo severity 16714 + minor stop On 02/10/2014 11:17 AM, Rachel Mant wrote: Hello, Attached is my test-log for automake 1.14.1 which sports

bug#16714: make check failures

2014-04-21 Thread Stefano Lattarini
On 04/21/2014 11:43 AM, Rachel Mant wrote: > On 21/04/14 11:21, Stefano Lattarini wrote: >> tags 16714 + moreinfo >> severity 16714 + minor >> stop >> >> On 02/10/2014 11:17 AM, Rachel Mant wrote: >>> Hello, >>> Attached is my test-log for automake 1.14.1 which sports an alarming >>> number

bug#16714: make check failures

2014-04-21 Thread Rachel Mant
On 21/04/14 11:21, Stefano Lattarini wrote: tags 16714 + moreinfo severity 16714 + minor stop On 02/10/2014 11:17 AM, Rachel Mant wrote: Hello, Attached is my test-log for automake 1.14.1 which sports an alarming number of failures despite having upgraded my system's m4 and autoconf

bug#16714: make check failures

2014-04-21 Thread Stefano Lattarini
tags 16714 + moreinfo severity 16714 + minor stop On 02/10/2014 11:17 AM, Rachel Mant wrote: > Hello, >Attached is my test-log for automake 1.14.1 which sports an alarming >number of failures despite having upgraded my system's m4 and >autoconf just fine to their newest versions. > It