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

[netCDF #EZD-873215]: netcdf on linux 2.6

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: [netCDF #EZD-873215]: netcdf on linux 2.6
  • Date: Fri, 01 Sep 2006 14:09:55 -0600
Hi Gaby,

re: 
> Hi there, I built using both ifort (Intel fortran) and gfortran.
> gfortran fails the make test, and in any event I read in the support
> archives that one should build the netCDF with the same compiler one's
> going to use, so I built it with ifort.

Yes, whenever possible you should not introduce uncertainty by using libraries
built using compliers different from the ones you are trying to use.

> It passes the tests and all seems OK,

Very good.

> but I don't seem to be able to compile my code w/o expressely
> including /home/turekg/local/lib/libnetcdf.a in the compile command
> (rather than using the -L compile switch).

If the binary netCDF installation you were trying to use was from
a package management system, and the libraries were installed in
system directories (e.g., /usr/local/lib), then it is likely that
your command line link specification is causing the package-installed
library to be search before the one you built.  If this is what is
happening, it would be best if you uninstalled the binary distribution
you were trying to use so that your newly built library will get
searched instead.

Completely specifying the library you built using something
like '-l/home/turekg/local/lib/libnetcdf.a' will force the library
to be searched for entry points while the specification
'-L/home/turekg/local/lib -lnetcdf' tells the linker
to search the /home/turekg/local/lib directory for libraries when
searching for missing entry points.  This might be occurring
_after_ searching of the netCDF library you installed from a
binary which you previously reported is missing the Fortran entry
points.

By the way, where did you get the binary netCDF library that you
were originally trying to use?  If you got it from us (Unidata),
then there may be a problem with it that needs to be fixed (i.e.,
it should not be missing Fortran entry points).


Cheers,

Tom
****************************************************************************
Unidata User Support                                    UCAR Unidata Program
(303) 497-8642                                                 P.O. Box 3000
address@hidden                                   Boulder, CO 80307
----------------------------------------------------------------------------
Unidata HomePage                       http://www.unidata.ucar.edu
****************************************************************************


Ticket Details
===================
Ticket ID: EZD-873215
Department: Support netCDF
Priority: Normal
Status: Closed