installation along with netcdf4.0 and gcc

[manishsoni0291]

Dear Users,

I am trying to install netcdf-4.0.1 in Linux of local PC ( Pentium IV) for ARW.
I am getting the error which is shown below.
Mainly, the error is coming from the installation of cfortran.h.
Let me know how to solve this.

Thanks in advance,

Manish Soni






Making check in fortran
make[1]: Entering directory `/home/server/Swagata/netcdf-4.0.1/fortran'
make check-am
make[2]: Entering directory `/home/server/Swagata/netcdf-4.0.1/fortran'
depbase=`echo fort-attio.lo | sed 's|[^/]*$|.deps/&|;s|\.lo$||'`;\
/bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I../libsrc4 -I/home/server/local/include -g -O2 -MT fort-attio.lo -MD -MP -MF $depbase.Tpo -c -o fort-attio.lo fort-attio.c &&\
mv -f $depbase.Tpo $depbase.Plo
libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../libsrc4 -I/home/server/local/include -g -O2 -MT fort-attio.lo -MD -MP -MF .deps/fort-attio.Tpo -c fort-attio.c -o fort-attio.o
In file included from ncfortran.h:12,
from fort-attio.c:7:
cfortran.h:138:3: #error "cfortran.h: Can't find your environment among: - MIPS cc and f77 2.0. (e.g. Silicon Graphics, DECstations, ...) - IBM AIX XL C and FORTRAN Compiler/6000 Version 01.01.0000.0000 - VAX VMS CC 3.1 and FORTRAN 5.4. - Alpha VMS DEC C 1.3 and DEC FORTRAN 6.0. - Alpha OSF DEC C and DEC Fortran for OSF/1 AXP Version 1.2 - Apollo DomainOS 10.2 (sys5.3) with f77 10.7 and cc 6.7. - CRAY - NEC SX-4 SUPER-UX - CONVEX - Sun - PowerStation Fortran with Visual C++ - HP9000s300/s700/s800 Latest test with: HP-UX A.08.07 A 9000/730 - LynxOS: cc or gcc with f2c. - VAXUltrix: vcc,cc or gcc with f2c. gcc or cc with f77. - f77 with vcc works; but missing link magic for f77 I/O. - NO fort. None of gcc, cc or vcc generate required names. - f2c : Use #define f2cFortran, or cc -Df2cFortran - NAG f90: Use #define NAGf90Fortran, or cc -DNAGf90Fortran - Absoft UNIX F77: Use #define AbsoftUNIXFortran or cc -DAbsoftUNIXFortran - Absoft Pro Fortran: Use #define AbsoftProFortran - Portland Group Fortran: Use #define pgiFortran - PathScale Fortran: Use #define PATHSCALE_COMPILER"
make[2]: *** [fort-attio.lo] Error 1
make[2]: Leaving directory `/home/server/Swagata/netcdf-4.0.1/fortran'
make[1]: *** [check] Error 2
make[1]: Leaving directory `/home/server/Swagata/netcdf-4.0.1/fortran'
make: *** [check-recursive] Error 1

[Kevin_D_Intel]

Judging from the output it appears the configure step failed perhaps related to not finding a Fortran compiler.

I see you posted the same message to this Knowledge Base article for building netcdf with Intel compilers (here), but perhaps you did not "source" the appropriate ifortvars.sh/ifortvars.csh setup script before running configure as discussed in the section titled Configuration and set-up information. You might also double check that you exported all the indicated environment variables.

[Mike_Rezny]

Quoting - Kevin Davis (Intel)

Judging from the output it appears the configure step failed perhaps related to not finding a Fortran compiler.

I see you posted the same message to this Knowledge Base article for building netcdf with Intel compilers (here), but perhaps you did not "source" the appropriate ifortvars.sh/ifortvars.csh setup script before running configure as discussed in the section titled Configuration and set-up information. You might also double check that you exported all the indicated environment variables.

Hi,
in the past (with 3.6 versions of NetCDF), I have had to define th efollowing environment variables to ensure
all th ecode was compiled using Intel Fortran and C compilers:
CC = icc
FC= ifort
F77 = ifort
F90 = ifort
CXX = '' (unless you actually need the C++ version of the netcdf library)
CPP = "icc -E"
CPPFLAGS = -DpgiFortran

You may also need to assign values to the following compiler options:
CFLAGS, FFLAGS, F90FLAGS, FCFLAGS, FCFLAGS_f90

Also, from memory, unless you really net HDF support, it is simpler to build the library without it.
You will need to read the install docs to find out how to disable HDF support.

The definitive part, once you get past the compiler errors is to ensure that 'make check' runs all the validation tests without ANY failures. I have learnt, from many wasted hours tracking down application problems, that there is no point linking any of the NetCDF libraries unless all the validation test have passed without error.

regards
Mike