Re: Trouble running the gfortran testsuite

[James E Wilson <wilson at specifixinc dot com>]

Volker Reichelt wrote:
> I've got trouble running the gfortran testsuite on mainline.
> Since I've got libgmp.so in a non-standard location, I added its path
> to the LD_LIBRARY_PATH.
> But running "make check-f95" from $(builddir)/gcc fails utterly, since
> f951 cannot load libgmp.so. The strange thing is, that it actually *works*
> for the first testcase and then fails for all subsequent tests:

The testsuite infrastructure sets LD_LIBRARY_PATH so that the libraries 
in the build tree can be found.  This allows testing from an uninstalled 
build to work.

Perhaps there is a logic error in this code that causes your value for 
LD_LIBRARY_PATH to be lost.  See the code in the function 
gfortran_link_flags in the file gcc/gcc/testsuite/lib/gfortran.exp.

You could try running dejagnu with verbose flags to see what it is 
doing, e.g.
  make check-f95 RUNTESTFLAGS="-v -v"
The more -v flags you add, the more verbosity you get.

You can try adding compiler options to run the linker in verbose mode to 
see what is going wrong, e.g. add "-Wl,--verbose" somewhere.  To the 
specs file, to the gfortran_link_flags function, etc.  There are many 
ways to accomplish this.
--
Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com