Re: Some remarks running the testsuite

[Benjamin Kosnik <bkoz at redhat dot com>]

Alexandre, I'm cc'ing you because libstdc++.so is not being generated 
correctly. As Peter points out in the email below, 

<bkoz@fillmore> 
/mnt/hd/ahimsa/bld-x86-gcc/i686-pc-linux-gnu/libstdc++-v3/src/.libs 
%ldd libstdc++.so.3.0.0 
	libm.so.6 => /lib/libm.so.6 (0x400c8000)
	libc.so.6 => /lib/libc.so.6 (0x400e8000)
	/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x80000000)
	libgcc_s.so.0 => not found

Hmm. Bad news, indeed.

Here's how libstdc++.so is being built on my x86/linux system:

/mnt/hd/ahimsa/bld-x86-gcc/gcc/xgcc -B/mnt/hd/ahimsa/bld-x86-gcc/gcc/ 
-nostdinc++  
-L/mnt/hd/ahimsa/bld-x86-gcc/i686-pc-linux-gnu/libstdc++-v3/src 
-L/mnt/hd/ahimsa/bld-x86-gcc/i686-pc-linux-gnu/libstdc++-v3/src/.libs 
-B/mnt/hd/bliss/H-x86-gcc/i686-pc-linux-gnu/bin/ 
-B/mnt/hd/bliss/H-x86-gcc/i686-pc-linux-gnu/lib/ -isystem 
/mnt/hd/bliss/H-x86-gcc/i686-pc-linux-gnu/include -shared -nostdlib 
/usr/lib/crti.o /mnt/hd/ahimsa/bld-x86-gcc/gcc/crtbeginS.o  
.libs/limitsMEMBERS.o .libs/stdexcept.o .libs/functexcept.o 
.libs/bitset.o .libs/globals.o .libs/basic_file.o .libs/ios.o 
.libs/complex_io.o .libs/strstream.o .libs/c++locale.o .libs/locale.o 
.libs/localename.o .libs/codecvt.o .libs/locale-inst.o .libs/stl-inst.o 
.libs/misc-inst.o .libs/valarray-inst.o .libs/string-inst.o 
.libs/wstring-inst.o -Wl,--whole-archive ../libmath/.libs/libmath.a 
../libsupc++/.libs/libsupc++convenience.a -Wl,--no-whole-archive  
-L/mnt/hd/ahimsa/bld-x86-gcc/i686-pc-linux-gnu/libstdc++-v3/src 
-L/mnt/hd/ahimsa/bld-x86-gcc/i686-pc-linux-gnu/libstdc++-v3/src/.libs -lm 
../libmath/.libs/libmath.a -lm ../libsupc++/.libs/libsupc++convenience.a 
-lm -L/mnt/hd/ahimsa/bld-x86-gcc/gcc -lm -lc -lgcc_s   
/mnt/hd/ahimsa/bld-x86-gcc/gcc/crtendS.o /usr/lib/crtn.o  -Wl,-soname 
-Wl,libstdc++.so.3 -o .libs/libstdc++.so.3.0.0
(cd .libs && rm -f libstdc++.so.3 && ln -s libstdc++.so.3.0.0 libstdc++.so.3)
(cd .libs && rm -f libstdc++.so && ln -s libstdc++.so.3.0.0 libstdc++.so)


??

On Tue, 3 Apr 2001, Peter Schmid wrote:

> After updating dejagnu to version 1.4.0 the testsuite finally
> runs. But since the binaries are not deleted after a successful run,
> the testsuite directory consumes 172 Mbytes. I believe that is too
> much space.  

yeah they should probably be removed after successful execution, like the 
last testsuite.

> peter@kiste:~/egcs/build/i686-pc-linux-gnu/libstdc++-v3 > du -ms testsuite
> 172	testsuite
> 
> Furthermore, the libgcc library located in /usr/local/lib is linked in,
> and not the copy located in the gcc build directory.
>  
> peter@kiste:~/egcs/build/i686-pc-linux-gnu/libstdc++-v3/testsuite/27_io > ldd istream.sh-exe 
> 	libstdc++.so.3 => /home/peter/egcs/build/i686-pc-linux-gnu/libstdc++-v3/src/.libs/libstdc++.so.3 (0x40018000)
> 	libm.so.6 => /lib/libm.so.6 (0x400e1000)
> 	libgcc_s.so.0 => /usr/local/lib/libgcc_s.so.0 (0x400ff000)
> 	libc.so.6 => /lib/libc.so.6 (0x40108000)
> 	/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
> 
> And finally, there are many regressions, I believe at least some of
> these are caused by the command line arguments "-lgcc_s -lgcc -lc
> -lgcc" for generating the executables.

Yeah. See above. We were down to just expected failures one week ago.

-benjamin