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

Re: 20050217: NETCDF Built Error on XEON

Unidata Support <address@hidden> writes:

> ------- Forwarded Message
>
>>To: <address@hidden>
>>cc: "Phung, Thanh" <address@hidden>
>>From: "Phung, Thanh" <address@hidden>
>>Subject: NETCDF Built Error on XEON
>>Organization: Intel
>>Keywords: 200502172315.j1HNFGv2022886 netCDF 3.6.1p1 Xeon
>
> Hi:
> I just tar-ed and they to build netcdf-3.6.0-p1 on my new XEON system to
> be used for WRF testing.
> 1. Is this netcdf version good for 32bit Xeon?
> 2. Here is the error I got from the built.  It looks to me that the flag
> setting is incorrect when you try to preprocess C code to .f code.
>
> Thanh Phung
>
> make[2]: Entering directory `/export/tphung/netcdf-3.6.0-p1/src/fortran'
> cc -c -g -I../libsrc   fort-attio.c
> In file included from ncfortran.h:13,
>                  from fort-attio.c:6:
> 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.o] Error 1
> make[2]: Leaving directory `/export/tphung/netcdf-3.6.0-p1/src/fortran'
> make[1]: *** [subdir_target] Error 1
> make[1]: Leaving directory `/export/tphung/netcdf-3.6.0-p1/src'
> make: *** [fortran/all] Error 2
>
> --
> NOTE: All email exchanges with Unidata User Support are recorded in the
> Unidata inquiry tracking system and then made publicly available
> through the web.  If you do not want to have your interactions made
> available in this way, you must let us know in each email you send to us.
>
> ------- End of Forwarded Message
>
>

You should try setting CPPFLAGS to -Df2cFortran. If that doesn't work,
try -DpgiFortran.

If neither work, we'll have to look further. Basically you need to set
CPPFLAGS to give the netCDF fortran code some idea what Fortran
compiler you are using. So what compiler are you using? For g77, use
Df2cFortran, for Portland Group fortran, use -DpgiFortran. For other
fortrans there are other choices.

THanks,

Ed


-- 
Ed Hartnett  -- address@hidden