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

[netCDF #VLT-558992]: Building the NetCDF-4.2 and Fortran libraries



Hello,

It appears that you have configured and built everything correctly; it is odd 
that this test is failing with this error.  It indicates an issue finding the 
netcdf-c library, however if this were the case I would have expected to see 
similar errors much, much earlier in the process.   When you built netcdf-c, 
did you build it with netcdf-4 support?

Does this error also occur if you try to run the test manually, instead of 
through `make check`?

-Ward

> Hi,
> 
> I'm having trouble in installing the NetCDF Fortran librarires. I
> managed to install HDF5 and build and installed the netCDF C library
> without errors. But when I try to build the Fortran libraries using
> 
> export LD_LIBRARY_PATH=/home/virtanet/netdf_4331/lib:${LD_LIBRARY_PATH}
> CPPFLAGS=-I/home/virtanet/netdf_4331/include
> LDFLAGS=-L/home/virtanet/netdf_4331/lib ./configure
> --prefix=/home/virtanet/netdf_4331f
> 
> and run make check,  I get the following error:
> 
> ftst_rengrps.F:49.48:
> 
> call check(nf_create(FILE_NAME, NF_NETCDF4, ncid))
> 1
> Error: Symbol 'nf_netcdf4' at (1) has no IMPLICIT type
> make[2]: *** [ftst_rengrps.o] Error 1
> 
> I have tried to find advice from the web, and have tried different
> approaches without success. Could you help me here? The config.log is
> attached.
> 
> Best regards,
> Timo
> 
> --
> 
> Dr. Timo H. Virtanen
> Finnish Meteorological Institute
> Climate Research Unit, Remote Sensing of Aerosols and Clouds
> P.O. Box 503, FI-00101 Helsinki, Finland
> Mobile: +358 50 4212 360
> Email: address@hidden
> 
> 
> 


Ticket Details
===================
Ticket ID: VLT-558992
Department: Support netCDF
Priority: Normal
Status: Closed


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.