bug-automake
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#10866: 1.11a OSX with llvm - 3 fails, 47 skips, 3 errors, out of 285


From: Stefano Lattarini
Subject: bug#10866: 1.11a OSX with llvm - 3 fails, 47 skips, 3 errors, out of 2856 tests
Date: Wed, 14 Mar 2012 21:06:34 +0100

Hi, and sorry for the delay.

On 03/12/2012 08:07 PM, P. Martin wrote:
> 
> Thanks for the patch.  It fixes test 1 so it skips not error.
>
Good, that is what it's supposed to do.  I've pushed it now.

> [SNIP]

> Results with 1.11a d63c932 :  2 Fail, 22 Skip, 0 Error, 2910 total.
> 
> Darn.  Those are back.  Same ones I started posting about.
> Because I've gone through three versions of XCode in the last two
> months, I really should do a clean install before we address these.
> For curiosity sake, I attached the latest log.  If something is obvious,
> let me know.  I can wait a day or two.

> FAIL: cond41.test
> ...
>
> + aclocal-1.11a -Werror
> + cat stderr
> configure.ac:5: error: AM_COND_IF: no such condition "BAD_COND"
> /private/tmp/homebrew-automake-HEAD-Khrp/m4/cond-if.m4:39: AM_COND_IF is 
> expanded from...
> configure.ac:5: the top level
> autom4te: /usr/bin/m4 failed with exit status: 1
> aclocal: error: autom4te failed with exit status: 1
> + grep '^configure\.ac:4:.*AM_COND_IF.* no such condition.*BAD_COND' stderr
> + exit_status=1
>
Weird and annoying, the line reported in the error message is off by one ...
I wouldn't loose my sleep on this, but it would be nice to understand the
reason of this racy failure; so I'm keeping the bug report open.

> FAIL: distcheck-override-infodir.test
> ...
>
> make[1]: Nothing to be done for `all'.
> TEXINPUTS="..:$TEXINPUTS" \
>  MAKEINFO='/bin/sh /.../missing --run makeinfo   -I ..' texi2dvi  ../main.texi
> sed: 2: "s/\(^\|.* \)@documenten ...": whitespace after branch
> sed: 4: "s/\(^\|.* \)@documenten ...": whitespace after label
> sed: 6: "s/\(^\|.* \)@documenten ...": undefined label 'found '
>
This seems either an issue with your sed, or with your texi2dvi installation...
Since that is from 2004 (almost 8 years old), and since texi2dvi is mostly a
maintainer tool, I wouldn't worry too deeply about this issue, assuming it is
not present with more modern Texinfo versions.

Thanks,
  Stefano





reply via email to

[Prev in Thread] Current Thread [Next in Thread]