------- Comment #3 from rob1weld at aol dot com 2009-01-25 17:35 ------- # ./e_d_fmt.exe Abort (core dumped)
# ldd ./e_d_fmt.exe libgfortran.so.3 => /usr/share/src/gcc_build/i386-pc-solaris2.11/./libgfortran/.libs/libgfortran.so.3 libm.so.2 => /usr/lib/libm.so.2 libgcc_s.so.1 => /usr/share/src/gcc_build/gcc/libgcc_s.so.1 libc.so.1 => /usr/lib/libc.so.1 # export set LD_LIBRARY_PATH=/usr/local/lib:/usr/lib:/opt/csw/lib:/usr/local/Trolltech/Qt-4.4.3/lib # ldd ./e_d_fmt.exe libgfortran.so.3 => /usr/local/lib/libgfortran.so.3 libm.so.2 => /usr/lib/libm.so.2 libgcc_s.so.1 => /usr/local/lib/libgcc_s.so.1 libc.so.1 => /usr/lib/libc.so.1 If I use the Testsuite's LD_LIBRARY_PATH then some of the Tests will load the wrong Libraries. If I use _my_ own LD_LIBRARY_PATH (as it is during configuration) then the Test programs use the correct Libraries and the programs run OK. In http://gcc.gnu.org/ml/gcc-testresults/2009-01/msg01790.html we only had array_constructor_23.f now we seem to have a few more. This is not so much an error in Fortran than it is an error in the scripting and it's ability to add it's own LD_LIBRARY_PATH components. Reducing the Severity to NORMAL. Thanks, Rob -- rob1weld at aol dot com changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|major |normal http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38946