LAM/MPI logo

LAM/MPI General User's Mailing List Archives

  |   Home   |   Download   |   Documentation   |   FAQ   |   all just in this list

From: Jeff Squyres (jsquyres_at_[hidden])
Date: 2003-07-03 08:56:38


On Thu, 3 Jul 2003, Andras Szabo wrote:

> I have downloaded lam-7.0 and installed it using the Intel Fortran and
> C++ compilers (version 7.1).

This is known behavior for the Intel compilers -- it's a problem with
the GNU Autoconf test. Please be sure to read the LAM/MPI
Installation and User's Guides -- we took a lot of trouble to write
them to provide this kind of information. :-)

>From the LAM/MPI Installation Guide, Section 8.2., "The LAM Test
Suite" (p38-39 -- pardon the LaTeX formatting below):

-----
\item Some Fortran compilers will confuse the GNU Autoconf fortran
  libraries test in the test suite's \cmd{configure} script (e.g.,
  some versions of the Intel Fortran compiler), causing the entire
  process to fail. If the ``checking for dummy main to link with
  Fortran 77 libraries'' test fails, set the \envvar{FLIBS}
  environment variable to the output of the ``checking for Fortran 77
  libraries'' test, but without the syntax errors that it incorrectly
  contains. For example (artificially word-wrapped to fit on the
  page):

\lstset{style=lam-shell}
\begin{lstlisting}
checking for Fortran 77 libraries... -L/u/jsquyres/local/lib
-llamf77mpi -lmpi -llam -lutil -lpthread'' -L\ -lpthread
-L/usr/local/intel/compiler70/ia32/lib -L/usr/lib -lintrins -lIEPCF90
-lF90 -limf -lm -lirc -lcxa -lunwind
checking for dummy main to link with Fortran 77 libraries... unknown
configure: error: linking to Fortran libraries from C fails
See `config.log' for more details.
\end{lstlisting}

  Note the extra quotes and empty ``{\tt -L}'' in the output. Remove
  these syntax errors when setting the \envvar{FLIBS} variable:

\lstset{style=lam-cmdline}
\begin{lstlisting}
shell$ FLIBS=``-L/u/jsquyres/local/lib -llamf77mpi -lmpi -llam -lutil \
-lpthread -L/usr/local/intel/compiler70/ia32/lib -L/usr/lib -lintrins \
-lIEPCF90 -lF90 -limf -lm -lirc -lcxa -lunwind''
shell$ export FLIBS
shell$ ./configure ...
\end{lstlisting}

  After setting \envvar{FLIBS} to this value, run \cmd{configure}
  again; the bad test will be skipped and \cmd{configure} will finish
  successfully.
-----

Hope this helps.

-- 
{+} Jeff Squyres
{+} jsquyres_at_[hidden]
{+} http://www.lam-mpi.org/