bug#12184: GNU Automake 1.12.2 - 4 tests FAIL on Solaris 10 Sparc

2012-08-14 Thread Stefano Lattarini
On 08/14/2012 02:20 AM, Dennis Clarke wrote: cc: 12...@debbugs.gnu.org On 08/13/2012 01:46 AM, Dennis Clarke wrote: At least I can get results in one hour now. :-\ [SNIP] Same as before: the only actual failure is: FAIL: t/silent-many-generic ===

bug#12184: GNU Automake 1.12.2 - 4 tests FAIL on Solaris 10 Sparc

2012-08-14 Thread Dennis Clarke
Hey man, get off my soap box! I was here first. :-) Yeah, I noticed too late :-) (after reading the latest messages in the bug-grep list). I went through a little pain with pcre also but sorted it all out by determining that the output makefiles were assuming Linux, as usual, and also

bug#12184: GNU Automake 1.12.2 - 4 tests FAIL on Solaris 10 Sparc

2012-08-14 Thread Stefano Lattarini
On 08/14/2012 05:30 PM, Dennis Clarke wrote: Hey man, get off my soap box! I was here first. :-) Yeah, I noticed too late :-) (after reading the latest messages in the bug-grep list). I went through a little pain with pcre also but sorted it all out by determining that the output

bug#12184: GNU Automake 1.12.2 - 4 tests FAIL on Solaris 10 Sparc

2012-08-14 Thread Dennis Clarke
http://bugs.exim.org/show_bug.cgi?id=1278 This should actually go to the grep list though, not to the automake one ... Or am I missing something? I as just illustrating that the portability issue is all over the place and in many software projects. It really doesn't matter if one looks

bug#12184: GNU Automake 1.12.2 - 4 tests FAIL on Solaris 10 Sparc

2012-08-14 Thread Stefano Lattarini
On 08/14/2012 07:33 PM, Dennis Clarke wrote: No ones fault other than the jerks at Sun followed by the much larger jerks at Oracle. While I might sympathize with your frustration, I *strongly* ask you to refrain from name-calling on this list. Using harsh words against problematic/buggy

bug#12184: GNU Automake 1.12.2 - 4 tests FAIL on Solaris 10 Sparc

2012-08-13 Thread Stefano Lattarini
On 08/13/2012 01:59 AM, Dennis Clarke wrote: My guess is that your grep (in /usr/local/bin/ggrep ) is busted. First clue: By the way, I did have one test with GNU grep fail and yes, I did file a report. The reply was not helpful : From Jim Meyering some email address Sent

bug#12184: GNU Automake 1.12.2 - 4 tests FAIL on Solaris 10 Sparc

2012-08-13 Thread Dennis Clarke
I suggest you try building with a recent version of gcc. If you really must use that other compiler, consider instrumenting the failing test to make it report the precise grep command that is failing. If you do, please report that, along with the actual/expected output. How is

bug#12184: GNU Automake 1.12.2 - 4 tests FAIL on Solaris 10 Sparc

2012-08-13 Thread Dennis Clarke
- Original Message - From: Stefano Lattarini stefano.lattar...@gmail.com Date: Monday, August 13, 2012 8:21 am Subject: Re: bug#12184: GNU Automake 1.12.2 - 4 tests FAIL on Solaris 10 Sparc To: Dennis Clarke dcla...@blastwave.org Cc: 12...@debbugs.gnu.org On 08/13/2012 01:46 AM

bug#12184: GNU Automake 1.12.2 - 4 tests FAIL on Solaris 10 Sparc

2012-08-13 Thread Dennis Clarke
cc: 12...@debbugs.gnu.org On 08/13/2012 01:46 AM, Dennis Clarke wrote: At least I can get results in one hour now. :-\ [SNIP] Same as before: the only actual failure is: FAIL: t/silent-many-generic === ... + make ld: fatal: file

bug#12184: GNU Automake 1.12.2 - 4 tests FAIL on Solaris 10 Sparc

2012-08-12 Thread Stefano Lattarini
On 08/12/2012 12:34 PM, Dennis Clarke wrote: From: Stefano Lattarini seems a problem in your compilers' setup rather than in the test itself. Could you please investigate whether this is the case? Certainly, I will go back and have another look more carefully. Thanks. Also, since I

bug#12184: GNU Automake 1.12.2 - 4 tests FAIL on Solaris 10 Sparc

2012-08-12 Thread Dennis Clarke
On 08/12/2012 08:59 PM, Dennis Clarke wrote: Wow .. things just got a LOT worse here. After nearly 7 hours : Testsuite summary for GNU Automake 1.12.2

bug#12184: GNU Automake 1.12.2 - 4 tests FAIL on Solaris 10 Sparc

2012-08-12 Thread Dennis Clarke
My guess is that your grep (in /usr/local/bin/ggrep ) is busted. First clue: By the way, I did have one test with GNU grep fail and yes, I did file a report. The reply was not helpful : From Jim Meyering some email address SentSunday, August 12, 2012 10:39 pm To Dennis Clarke