Hi Dennis, thanks for the report.

On 12/31/2012 09:19 AM, Dennis Clarke wrote:
> 
> Happy New Year  ;-)
> 
> ============================================================================
> Testsuite summary for GNU Automake 1.12.6
> ============================================================================
> # TOTAL: 2879
> # PASS:  2773
> # SKIP:  65
> # XFAIL: 39
> # FAIL:  2
> # XPASS: 0
> # ERROR: 0
> ============================================================================
> See ./test-suite.log
> Please report to bug-automake@gnu.org
> ============================================================================
> 
Yay, finally a decent testsuite behaviour :-)

So, let's look in more detail at those two failures ...

> FAIL: t/cxx-lt-demo
> ===================
>
> [SNIP]
>
> + /usr/local/bin/gmake -e
> Making all in lib
> gmake[1]: Entering directory 
> `/usr/local/build/automake-1.12.6_SunOS5.10_sparcv9/t/cxx-lt-demo.dir/lib'
> echo '#include <string>' >libfoo.h++-t
> grep "target *(" "./libfoo.c++" >>libfoo.h++-t
> echo ';' >>libfoo.h++-t
> chmod a-w libfoo.h++-t && mv -f libfoo.h++-t libfoo.h++
> /usr/local/bin/gmake  all-am
> gmake[2]: Entering directory 
> `/usr/local/build/automake-1.12.6_SunOS5.10_sparcv9/t/cxx-lt-demo.dir/lib'
> /usr/local/bin/libtool --tag=CXX   --mode=compile /usr/local/gcc4/bin/g++ \
>   -DPACKAGE_NAME=\"GNU\ C++/Libtool\ Demo\" 
> -DPACKAGE_TARNAME=\"c---libtool-demo\" \
>   -DPACKAGE_VERSION=\"0.73\" -DPACKAGE_STRING=\"GNU\ C++/Libtool\ Demo\ 
> 0.73\" \
>   -DPACKAGE_BUGREPORT=\"bug-automake@gnu.org\" \
>   -DPACKAGE_URL=\"http://www.gnu.org/software/c---libtool-demo/\"; \
>   -DPACKAGE=\"c---libtool-demo\" -DVERSION=\"0.73\" -DSTDC_HEADERS=1 \
>   -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 
> -DHAVE_STRING_H=1 \
>   -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 \
>   -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" \
>   -I.  -I/usr/local/include:/usr/local/gcc4/include  -mno-app-regs -mcpu=v9 \
>   -m64 -mptr64 -g -D_POSIX_PTHREAD_SEMANTICS -D_LARGEFILE64_SOURCE 
> -D_TS_ERRNO \
>   -MT libfoo.lo -MD -MP -MF .deps/libfoo.Tpo -c -o libfoo.lo libfoo.c++
> libtool: compile:  /usr/local/gcc4/bin/g++ "-DPACKAGE_NAME=\"GNU C++/Libtool 
> Demo\"" ...\
>   -MT libfoo.lo -MD -MP -MF .deps/libfoo.Tpo -c libfoo.c++ -KPIC -DPIC -o 
> .libs/libfoo.o
> g++: error: unrecognized command line option '-KPIC'
> gmake[2]: *** [libfoo.lo] Error 1
> gmake[2]: Leaving directory 
> `/usr/local/build/automake-1.12.6_SunOS5.10_sparcv9/t/cxx-lt-demo.dir/lib'
>
This failure seems actually due to a Libtool bug rather than an
Automake one, since Autoamke does not fiddle with these compiler
flags itself.  So we can safely ignore it here (if you feel like
writing a smaller reproducer and reporting the issue to the
Libtool list, you're of course very welcome to do so ;-)

> FAIL: t/silent-many-generic
> ===========================
> + /usr/local/bin/gmake
> baz3.f:
>       foo3:
> ld: fatal: file baz2.o: wrong ELF class: ELFCLASS32
> ld: fatal: file processing errors. No output written to baz
> collect2: error: ld returned 1 exit status
> gmake[3]: *** [baz] Error 1
> gmake[2]: *** [all] Error 2
> gmake[1]: *** [all-recursive] Error 1
> gmake: *** [all] Error 2
>
I'm a little lost here.  Perhaps a mismatch between the object files
generated by the GNU C/C++ compilers and the non-GNU Fortran ones?
What happens if you re-run this test forcing $FC and $F77 to point
to GNU compilers?  And what if you re-run it forcing $CC and $CXX
to point to non-GNU compilers?

> gcc_spec_node002 $ uname -a 
> SunOS node002 5.10 Generic_147440-23 sun4v sparc SUNW,T5240
> gcc_spec_node002 $ 
> gcc_spec_node002 $ cat /etc/release 
>                    Oracle Solaris 10 8/11 s10s_u10wos_17b SPARC
>   Copyright (c) 1983, 2011, Oracle and/or its affiliates. All rights reserved.
>                             Assembled 23 August 2011
> 
> 
> I'm sure everything is in the log file attached 
> 
> Dennis Clarke 
> dcla...@blastwave.org
> 
> ps: the testsuite is one obscene long process .. time -p says : 
> 
> real 28915.31
> user 15317.85
> sys 5091.92
> 
>    eeek.
> 
In you have a decent machine, you should try running make in concurrent
mode to speed-up the process; as in, say:

    $ make check -j16

Regards,
  Stefano

P.S. Automake 1.13 is out ;-)
<http://savannah.gnu.org/forum/forum.php?forum_id=7467>



Reply via email to