[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

20050422: Linux 32-bit Absoft & Intel "make nf_test/test" failure

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: 20050422: Linux 32-bit Absoft & Intel "make nf_test/test" failure
  • Date: Fri, 22 Apr 2005 11:30:24 -0600
Rene,

>Date: Fri, 22 Apr 2005 12:08:49 +0200
>From: Rene Redler <address@hidden>
>Organization: ?
>To: Steve Emmerson <address@hidden>
>Subject: Re: 20050421: more fortran tests with pnetcdf

The above message contained the following:

> I had some problems when installing the nf_test software with the
> Absoft  Fortran Compiler + ( gcc and g++).  I ended up with lots of 
> undefined  symbols (setenv CFLAGS -DAbsoftUNIXFortran for cfortran.h)

Is the name of the Absoft C compiler "gcc"?

What is the name of

    1.  the Absoft Fortran compiler;
    2.  the Intel C compiler; and
    3.  the Intel Fortran compiler?

The C and Fortran compilers in the "test.log" file that you sent me are
"gcc" and "ifort", respectively.  Does this mean that you used the
Absoft C compiler with the Intel Fortran compiler?  If not, then what
combination did you use?

> Since I could not find any support for the Intel compiler in the
> cfortran.h you ship with your distribution, I took some of my old
> cfortran.h (which someone -perhaps myslef - once modified to
> support the Intel Fortran compiler) and redid the configure + make
> with the latest version of the Intel Fortran Compiler.
> 
> The cfortran.h I've been using is attached to this mail as well
> as the output from running "make test".

The Intel Fortran compiler uses the same calling conventions as the
Portland Group Fortran compiler.  The "cfortran.h" file that you sent
basically uses the "pgiFortran" definitions -- so it should work for the
Intel Fortran compiler.

Alternatively, when using the Intel Fortran compiler, you can use the
"cfortran.h" file that comes with the distribution if the environment
variable CPPFLAGS defines the C macro "pgiFortran" before the configure
script is executed, e.g.,

    export CPPFLAGS="-DpgiFortran"
    ./configure ...

Also, when using the Intel Fortran compiler, try setting the following
environment variables to the indicated values before executing the
configure script:

    export FLIBS="-L/opt/intel/compiler70/ia32/lib -lPEPCF90"
    FFLAGS="-O -mp"

You might have to adjust the pathname in the FLIBS variable.  The "-mp"
option is NECESSARY to obtain a successful "make test".

When using the Absoft Fortran compiler, try defining the C macro
"AbsoftProFortran" (rather than "AbsoftUNIXFortran") before executing
the configure script, e.g.,

    export CPPFLAGS="-DAbsoftProFortran"
    ./configure ...

Regards,
Steve Emmerson