> * Dennis Clarke wrote on Fri, Mar 21, 2008 at 02:28:23PM CET: >> Failed tests: >> GNU Autoconf 2.61 test suite test groups: >> >> NUM: FILE-NAME:LINE TEST-GROUP-NAME >> KEYWORDS >> >> 142: fortran.at:33 GNU Fortran 77 >> 143: fortran.at:61 GNU Fortran >> 144: acfortran.at:12 AC_F77_MAIN >> 145: acfortran.at:13 AC_F77_WRAPPERS >> 146: acfortran.at:14 AC_FC_MAIN >> 147: acfortran.at:15 AC_FC_WRAPPERS >> 148: acfortran.at:16 AC_PROG_F77_C_O >> 149: acfortran.at:17 AC_PROG_FC_C_O > >> 142. fortran.at:33: testing ... > [...] >> > configure:1821: checking for Fortran 77 compiler default output file >> name >> > configure:1848: gfortran conftest.f >&5 >> > configure:1851: $? = 0 >> > configure:1889: result: a.out >> > configure:1906: checking whether the Fortran 77 compiler works >> > configure:1916: ./a.out >> > ./a.out: error while loading shared libraries: libgfortran.so.2: cannot >> open shared object file: No such file or directory >> > configure:1919: $? = 127 >> > configure:1928: error: cannot run Fortran 77 compiled programs. >> > If you meant to cross compile, use `--host'. >> > See `config.log' for more details. > > Your gfortran installation is not working as desired, more specifically, > the runtime linker can't find libgfortran.so.2. You can probably get > the tests to pass with something like > LDFLAGS=-Wl,-rpath,/path/to/gfortran-prefix/lib > export LDFLAGS > make check TESTSUITEFLAGS='-k ".*77.*" -k ".*_FC_.*"' > > or by fixing the gcc.spec to add the run path by default. Or setting > LD_LIBRARY_PATH suitably.
I'll try LD_LIBRARY_PATH as something somewhere may be assuming that /usr/local/lib is the right place to look .. and in this case it isn't. Not yet anyways. Thank you for the reply and the hint. Dennis
