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

Re: 20050217: NETCDF Built Error on XEON

>To: <address@hidden>
>cc: "Phung, Thanh" <address@hidden>
>From: "Phung, Thanh" <address@hidden>
>Subject: NETCDF Built Error on XEON
>Organization: UCAR/Unidata
>Keywords: 200502172315.j1HNFGv2022886

Hi Thanh,

> 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?

Yes, there is only one version that should work on all platforms,
including 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.
 ...

What compilers are you using for C and Fortran?  What operating system
are you using?  It's possible that you need to set some
compiler-dependent environment variables before running the configure
script.  For example, if you are using the Intel ifort 8.1 Fortran
compiler, see

  http://www.unidata.ucar.edu/packages/netcdf/other-builds.html#Linux_ifort-360

for building on Linux, and there are other examples of settings that
work for various combinations of platforms and compilers that we don't
have access to in:

  http://www.unidata.ucar.edu/packages/netcdf/other-builds.html

If these don't work for you, please see this page:

  
http://my.unidata.ucar.edu/content/software/netcdf/netcdf-install/If-Something-Goes-Wrong.html#If-Something-Goes-Wrong

for how to report problems so that we can diagnose them.  Thanks!

--Russ