Open MPI logo

Open MPI User's Mailing List Archives

  |   Home   |   Support   |   FAQ   |   all Open MPI User's mailing list

From: Jeff Squyres (jsquyres_at_[hidden])
Date: 2006-02-27 06:18:45

On Feb 24, 2006, at 12:17 PM, Pierre Valiron wrote:

> *** Fortran 90/95 compiler
> checking whether we are using the GNU Fortran compiler... no
> checking whether f95 accepts -g... yes
> checking for Fortran flag to compile .f files... none
> checking for Fortran flag to compile .f90 files... none
> checking whether f77 and f95 compilers are compatible... no
> configure: WARNING: *** Fortran 77 and Fortran 90 compilers are not
> link compatible
> configure: WARNING: *** Disabling Fortran 90/95 bindings

I see the problem here:

configure:32389: f95 -o conftest conftestf90.o conftestf77.o
ld: fatal: file conftestf77.o: wrong ELF class: ELFCLASS64

We do a test in configure to check that both compilers are link-
compatible to ensure that we don't run into any unexpected problems
later. The problem here is that the f77 test file was compiled with
the proper 64 bit flags, but the f90 test was not. This comes from a
typo in your openmpi-build-icare.csh script. The following line:

FCLAGS "-O -xtarget=opteron -xarch=amd64"

should be:

setenv FCFLAGS "-O -xtarget=opteron -xarch=amd64"

(i.e., "FCFLAGS", not "FCLAGS").

> Then the make fails in orte/mca/pls/base with message
> "pls_base_context.c", line 48: undefined symbol: MAXHOSTNAMELEN

Oops. This is my fault from a recent commit. We fixed this, and
after doing some sample builds with Sun Studio 11 on Solaris/SPARC
(this is not one of the compilers/platforms we test with on a regular
basis yet) we found another pair of minor issues that have now also
been fixed. Specifically, we think that these were Solaris issues --
not SPARC issues.

I just put 1.0.2a9 on the web site with all these fixes. Can you
give it a whirl and let us know how it goes?

{+} Jeff Squyres
{+} The Open MPI Project