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

20030501: netCDF build problem on Linux: cfortran.h

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: 20030501: netCDF build problem on Linux: cfortran.h
  • Date: Thu, 01 May 2003 08:51:11 -0600
Jiping,

>Date: Thu, 1 May 2003 10:23:58 -0400 (EDT)
>From: Jiping Liu <address@hidden>
>Organization: Georgia Tech
>To: Steve Emmerson <address@hidden>
>Subject: Re: 20030430: netCDF build problem on Linux: cfortran.h 

The above message contained the following:

> Thanks for your help. I put my test.log and install.log as follows.
> It seems everything is ok. Is that right?

Yes.  Your build and installation went OK.

> However, when I run 
> ncdump, I got bash: ncdump: command not found. Do I need to
> set up something in my .bashrc file?

The bash(1) user-shell needs to know where to find the ncdump(1)
utility.  Typically, this is done by appropriately setting the PATH
environment variable.  In your situation, you should ensure that it
references the directory "/usr/local/netcdf-3.5.1-beta10/bin".

> Additionally, assume there is no problem with netcdf install,
> when I compile a fortran program, what kind parameters I shoud
> use. For example, f77 -o test xxxx test.f xxxxx.

Typically, you will need to reference the netCDF header-file directory
and the netCDF library, e.g.,

    f77 ... -I /usr/local/netcdf-3.5.1-beta10/include ... \
        -L /usr/local/netcdf-3.5.1-beta10/lib -lnetcdf

For more information, please consult the netCDF documentation.

Regards,
Steve Emmerson