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

Re: 20050329: netcdf 3.6.0p1 opteron cluster

Unidata Support <address@hidden> writes:

> ------- Forwarded Message
>
>>To: address@hidden
>>From: Tim Hoar <address@hidden>
>>Subject: netcdf 3.6.0p1 opteron
>>Organization: NCAR/CGD
>>Keywords: 200503290038.j2T0cRv2018149 netCDF configure Intel Fortran 8.1
>
>   This message is in MIME format.  The first part should be readable text,
>   while the remaining parts are likely unreadable without MIME-aware tools.
>   Send mail to address@hidden for more info.
>
> ---559023410-838545539-1112056702=:23626
> Content-Type: TEXT/PLAIN; charset=US-ASCII
>
> We are just getting the Intel compilers (V8.1) on 'lightning' - the 128-node
> Opteron cluster in SCD.
>
> All attempts at building the Fortran interfaces for V3.5.1 and V3.6.0p1
> fail.  It's like 'config' cannot figure out the fortran type for the
> C type.

This is the case. The Intel fortran compiler is not one of the ones
that netCDF automatically configures for in the 3.6.0p1 release. I
hope to add this to the 3.6.1 release, and subsequent releases. As you
can imagine, customizing the configure for new compilers is an ongoing
chore, and I only got my local copy of Intel fortran a little while
ago.

>
> I have read and used the tipf for 'other-builds.html'
> http://my.unidata.ucar.edu/content/software/netcdf/docs/other-builds.html#Linux_ifort-360
>    as pertains to "Linux x86 with Intel ifort 8.1 fortran compiler'
>
> BTW - the one by Arnaud Desitter cannot possibly create the F90
> interface.

Why not?

> The one by Richard P. Signell is what has worked for me with the 8.0 Intel
> compiler on other architectures, but does not work on lightning.
> Also -- the 'successful build output' link is broken.

Sorry, I've fixed that. Try the settings there and see if they work
for you. 

source ~/local/bin/ifortvars.sh 
sh-3.00$ export CPPFLAGS=-DpgiFortran
sh-3.00$ export FC=ifort
sh-3.00$ export FFLAGS="-g -O2 -mp -recursive"

(Note that I have to source ifortvars.sh to get the intel compiler to
work on my machine - perhaps you are executing this automatically on
login, or something like that.)

Sorry, but my mail reader tells me that your BASE64 message below is
not right. I wonder if you could send the output of configure and make
test as plain ascii.

(Don't forget to do a make distclean before retrying the build).

Please let me know how this works out for you.

Thanks,

Ed

-- 
Ed Hartnett  -- address@hidden