Why Remove libstdc++-v3-dg.exp's Irix code?
Jeffrey Oldham
oldham@codesourcery.com
Tue Aug 14 15:42:00 GMT 2001
Your 07Aug libstdc++-v3 changes included removing this code from 3.1's
libstdc++-v3/testsuite/lib/libstdc++-v3-dg.exp:
- # On IRIX 6, we have to set variables akin to LD_LIBRARY_PATH, but
- # called LD_LIBRARYN32_PATH (for the N32 ABI) and LD_LIBRARY64_PATH
- # (for the 64-bit ABI). The right way to do this would be to modify
- # unix.exp -- but that's not an option since it's part of DejaGNU
- # proper, so we do it here, by trickery. We really only need to do
- # this on IRIX, but it shouldn't hurt to do it anywhere else.
- proc libstdc++-v3_set_ld_library_path { name element op } {
- setenv LD_LIBRARYN32_PATH [getenv LD_LIBRARY_PATH]
- setenv LD_LIBRARY64_PATH [getenv LD_LIBRARY_PATH]
- }
-
- trace variable env(LD_LIBRARY_PATH) w libstdc++-v3_set_ld_library_path
Without it, all libstdc++-v3 execution tests fail for mips-sgi-irix6.5
gcc 3.1. May we have it returned to the mainline branch?
I have attached:
1) the patch
2) a summary of the libstdc++-v3 regression tests results without
using the patch (along with other results)
Thanks,
Jeffrey D. Oldham
oldham@codesourcery.com
Index: testsuite/lib/libstdc++-v3-dg.exp
===================================================================
RCS file: /cvs/gcc/egcs/libstdc++-v3/testsuite/lib/libstdc++-v3-dg.exp,v
retrieving revision 1.7
retrieving revision 1.8
diff -c -p -r1.7 -r1.8
*** libstdc++-v3-dg.exp 2001/08/07 03:38:33 1.7
--- libstdc++-v3-dg.exp 2001/08/08 02:49:01 1.8
*************** proc libstdc++-v3_target_compile { sourc
*** 156,170 ****
return [target_compile $source $dest $type $options]
}
- # On IRIX 6, we have to set variables akin to LD_LIBRARY_PATH, but
- # called LD_LIBRARYN32_PATH (for the N32 ABI) and LD_LIBRARY64_PATH
- # (for the 64-bit ABI). The right way to do this would be to modify
- # unix.exp -- but that's not an option since it's part of DejaGNU
- # proper, so we do it here, by trickery. We really only need to do
- # this on IRIX, but it shouldn't hurt to do it anywhere else.
- proc libstdc++-v3_set_ld_library_path { name element op } {
- setenv LD_LIBRARYN32_PATH [getenv LD_LIBRARY_PATH]
- setenv LD_LIBRARY64_PATH [getenv LD_LIBRARY_PATH]
- }
-
- trace variable env(LD_LIBRARY_PATH) w libstdc++-v3_set_ld_library_path
--- 156,158 ----
More information about the Gcc-bugs
mailing list