Re: [jamboost] Re: V2 testing

From: Vladimir Prus (ghost_at_[hidden])
Date: 2004-09-21 04:45:23

Vincent Jamart wrote:

> Our QA procedure tests also run the test_all.py on bjam v2 for the
> http://cvs.sourceforge.net/cvstarballs/boost-*.tar code every night

Thanks! It's a great contribution.

> The results for
> -AIX 5.1/vacpp 6.0 (64bit)
> -Solaris9/gcc 3.3.1 (64bit)
> -Irix 6.5/MiprsPRO 7.4 (64bit)
> -Athlon(x86-32) GNU/Linux 2.4.21 (SuSE 9.0)/gcc 3.3.1
> -AthlonMP1900+(x86-32) GNU/Linux 2.4.18-smp (RedHat 8.0)/icc 8.0

There are some problems:
> -AIX 5.1/vacpp 6.0 (64bit)
> -Irix 6.5/MiprsPRO 7.4 (64bit)

The logs appear to be truncated. Maybe, it's some glitch on the server, or in 
Python on those platforms?

> -AthlonMP1900+(x86-32) GNU/Linux 2.4.18-smp (RedHat 8.0)/icc 8.0

The test result indicate that gcc is being used, not icc.

> -Athlon(x86-32) GNU/Linux 2.4.21 (SuSE 9.0)/gcc 3.3.1

Some of the test failures say that you did not configure "icc" correctly on 
that box. Anyway, it's not a big problem.

> -Solaris9/gcc 3.3.1 (64bit)

Here, there's a lot of errors like:

ld: fatal: file bin/gcc/debug/a.o: wrong ELF class: ELFCLASS64

What could be wrong? Does ld needs some switch to operate in 64-bit mode?

Thanks,
Volodya