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

From: Dennis Clarke <[email-masked]>
Date: Sun, 12 Aug 2012 10:34:10 +0000 (GMT)

----- Original Message -----
From: Stefano Lattarini <[email-masked]>
Date: Sunday, August 12, 2012 9:20 am
Subject: Re: bug#12184: GNU Automake 1.12.2 - 4 tests FAIL on Solaris 10 Sparc
To: Dennis Clarke <[email-masked]>
Cc: [email-masked]

> tags 12184 + moreinfo
> severity 12184 minor
> thanks
> 
> On 08/12/2012 07:33 AM, Dennis Clarke wrote:
> > ============================================================================
> > Testsuite summary for GNU Automake 1.12.2
> > ============================================================================
> > # TOTAL: 2578
> > # PASS:  2257
> > # SKIP:  271
> > # XFAIL: 46
> > # FAIL:  4
> > # XPASS: 0
> > # ERROR: 0
> > ============================================================================
> > See ./test-suite.log
> > Please report to [email-masked]
> > ============================================================================
> > 
> > See testsuite log, large, compressed, attached. 
> >
> Thanks.  The failures in 't/self-check-exit' and 't/self-check-explicit-skips'
> are just testsuite weaknesses, and they have already been fixed 
> recently, so
> no need to worry about them.
> 
> The error in 't/silent-many-generic':
> 
>   + make
>   ld: fatal: file baz2.o: wrong ELF class: ELFCLASS32
>   ld: fatal: file processing errors. No output written to baz
>   make: Fatal error: Command failed for target `baz'
>   ...
>   The following command caused the error:
>   echo "  CXXLD   " baz;am--cxx  -erroff -m64 -R/usr/local/lib 
> -L/usr/local/lib \
>       -mc -xO3 -xs -D_TS_ERRNO  -o baz baz1.o baz2.o baz3.o  baz5.o 
> baz6.o -ll
>   *** Error code 1
> 
> 
> 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. 

Also, since I am running these tests and they do take forever we may as well deal with "performance tests not explicitly enabled". 

How does one enable such tests ? Something to do with EXPENSIVE_TESTS or similar ? 

Dennis