The NetCDF Installation and Porting Guide

NetCDF Version 3.6.1

31 January 2006

Ed Hartnett, Russ Rew, John Caron

Unidata Program Center
Copyright
c 2005-2006 University Corporation for Atmospheric Research

Permission is granted to make and distribute verbatim copies of this manual provided that
the copyright notice and these paragraphs are preserved on all copies. The software and any
accompanying written materials are provided “as is” without warranty of any kind. UCAR
expressly disclaims all warranties of any kind, either expressed or implied, including but not
limited to the implied warranties of merchantability and fitness for a particular purpose.
The Unidata Program Center is managed by the University Corporation for Atmospheric
Research and sponsored by the National Science Foundation. Any opinions, findings, con-
clusions, or recommendations expressed in this publication are those of the author(s) and
do not necessarily reflect the views of the National Science Foundation.
Mention of any commercial company or product in this document does not constitute an
endorsement by the Unidata Program Center. Unidata does not authorize any use of
information from this publication for advertising or publicity purposes.
 i

Table of Contents

1 Installing the NetCDF Binaries . . . . . . . . . . . . . 1

2 Quick Instructions for Installing NetCDF on

Unix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

3 Building and Installing NetCDF on Unix

Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
3.1 Installation Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
3.2 Specifying the Environment for Building . . . . . . . . . . . . . . . . . . . . . . 6
3.3 Building on 64 Bit Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.4 Running the configure Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.5 Running make . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
3.6 Testing the Build . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
3.7 Installing NetCDF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
3.8 Platform Specific Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
3.8.1 AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
3.8.2 Cygwin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
3.8.3 HPUX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
3.8.4 Irix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
3.8.5 Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
3.8.6 Macintosh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.8.7 OSF1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.8.8 SunOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.8.9 Handling Fortran Compilers . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.9 Additional Porting Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

4 Building and Installing NetCDF on Windows

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
4.1 Getting Prebuilt netcdf.dll . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
4.2 Installing the DLL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
4.3 Building netcdf.dll with VC++ 6.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
4.4 Using netcdf.dll with VC++ 6.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
4.5 Building netcdf.dll with VC++.NET . . . . . . . . . . . . . . . . . . . . . . . . . . 18
4.6 Using netcdf.dll with VC++.NET . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

5 If Something Goes Wrong . . . . . . . . . . . . . . . . . 21

5.1 The Usual Build Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
5.1.1 Taking the Easy Way Out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
5.1.2 How to Clean Up the Mess from a Failed Build . . . . . . . . . . 21
5.1.3 Platforms On Which NetCDF is Known to Work . . . . . . . . . 21
5.1.4 Platforms On Which NetCDF is Reported to Work . . . . . . . 21
ii NetCDF Installation and Porting Guide

5.1.5 If You Have a Broken Compiler . . . . . . . . . . . . . . . . . . . . . . . . . 22

5.1.6 What to Do If NetCDF Still Won’t Build . . . . . . . . . . . . . . . . 22
5.2 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
5.2.1 Problems During Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 22
5.2.2 Problems During Compilation . . . . . . . . . . . . . . . . . . . . . . . . . . 23
5.2.3 Problems During Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
5.3 Finding Help On-line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
5.4 Reporting Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Chapter 1: Installing the NetCDF Binaries 1

1 Installing the NetCDF Binaries

At NetCDF World Headquarters hundreds of programmers labor around the clock to make
netCDF easier to get and use.
Perhaps the easiest way to get netCDF is to get a pre-built binary distribution. To get
them, see http://www.unidata.ucar.edu/software/netcdf/binaries.html.
To install the binary distribution, uncompress and unpack the tar file. You will end up
with 4 subdirectories, lib, include, man, and bin.
The lib subdirectory holds the netCDF library. The include directory holds the necessary
netcdf.h file. The bin directory holds the ncgen and ncdump utilities, and the man directory
holds the netCDF documentation.
You can have these directories anywhere you like, and use netCDF. But when compiling
a netCDF program, you will have to tell the linker where to find the library (e.g. with the
-L option of most C compilers), and you will also have to tell the C pre-processor where to
find the include file (e.g. with the -I option).
2 NetCDF Installation and Porting Guide
Chapter 2: Quick Instructions for Installing NetCDF on Unix 3

2 Quick Instructions for Installing NetCDF on

Unix
Who has time to read long installation manuals these days?
To install netCDF, uncompress and unpack the tar file, then change to the src directory:
gunzip netcdf-3.6.1.tar.gz
tar -xf netcdf-3.6.1.tar
cd netcdf-3.6.1/src
Now run the usual configure, make check, make install cycle:
./configure
make check
make install
The configure script will try to find necessary tools in your path. When you run config-
ure you may optionally use the –prefix argument to change the default installation direc-
tory. For example, the following will install the library in /usr/local/lib, the header file in
/usr/local/include, and the utilities in /usr/local/bin.
./configure --prefix=/usr/local
The default install root is .. (i.e. the parent directory, which will be netcdf-3.6.1).
If all this doesn’t work, then you might have to read the next chapter. Better luck next
time!
4 NetCDF Installation and Porting Guide
Chapter 3: Building and Installing NetCDF on Unix Systems 5

3 Building and Installing NetCDF on Unix

Systems
The latest version of this document is available at http://www.unidata.ucar.edu/software/netcdf/docs/ne
This document contains instructions for building and installing the netCDF package from
source on various platforms. Prebuilt binary releases are (or soon will be) available for var-
ious platforms from http://www.unidata.ucar.edu/software/netcdf/binaries.html.

3.1 Installation Requirements

Depending on the platform, you may need up to 25 Mbytes of free space to unpack, build,
and run the tests. You will also need a Standard C compiler. If you have compilers for
FORTRAN 77, FORTRAN 90, or C++, the corresponding netCDF language interfaces may
also be built and tested. Compilers and associated tools will only be found if they are in
your path.
If you want to run the large file tests, you will need about 13 GB of free disk space, as
some very large files are created. The created files are immediately deleted after the tests
complete. These large file tests are not run as part of the make check step; they are only
run for make extra check.
If you wish to build from source on a Windows (Win32) platform, different instructions
apply. See Chapter 4 [Building and Installing NetCDF on Windows], page 15.
To fully work with the netCDF source code, several extra utilities are required to fully
build everything from source. If you are going to modify the netCDF source code, you will
need some or all of the following Unix tools.
m4 Macro processing language used heavily in libsrc, nc test. Generates (in these
cases) C code from m4 source. Version 1.4 works fine with release 3.5.1 through
3.6.1.
nm Lists contents of an “object” file. GNU nm does not mix well with vendor
compilers in the 64-bit world, so make sure that you are using GNU nm with
GNU compilers, or a vendor nm with your vendor compiler.
ar Creates libraries. GNU ar does not mix well with vendor compilers in the 64-
bit world, so make sure that you are using GNU ar with GNU compilers, or a
vendor ar with your vendor compiler.
The following tools are not required to build netCDF. They may be needed if you intend
to work with the netCDF source code as a developer.
flex and yacc
Used in ncgen directory to parse CDL files. Generates C files from .y and .l files.
You only need to use this to modify ncgen’s understanding of CDL grammar.
makeinfo Generates all documentation formats (except man pages) from texinfo source.
I’m using makeinfo version 4.2, as of release 3.6.0. If you have trouble with
makeinfo, upgrade to at least 4.2 and try again. You only need makeinfo if you
want to modify the documentation.
autoconf Generates the configure script. Autoconf is only needed to modify the configure
script. Version 2.59 or later is required. Automake is not used with netCDF
version 3.6.
6 NetCDF Installation and Porting Guide

The most recent version of all netCDF documents can always be found at the netCDF
website. http://www.unidata.ucar.edu/software/netcdf.

3.2 Specifying the Environment for Building

The netCDF configure script will set some environment variables that are important for
building from source code. It is only necessary to set them to override default behavior.

The netCDF configure script searches your path to find the compilers and tools it needed.
To use compilers that can’t be found in your path, set their environment variables.

When finding compilers, vendor compilers will be preferred to GNU compilers. Not
because we don’t like GNU, but because we assume if you purchased a compiler, you want
to use it. Setting CC allows you to over-ride this preference. (Alternatively, you could
temporarily remove the compiler’s directories from your PATH.)

For example, on an AIX system, configure will first search for xlc, the AIX compiler. If
not found, it will try gcc, the GNU compiler. To override this behavior, set CC to gcc (in
sh: export CC=gcc). (But don’t forget to also set CXX to g++, or else configure will try
and use xlC, the AIX C++ compiler.)

By default, the netCDF library is built with assertions turned on. If you wish to turn
off assertions, set CPPFLAGS to -DNDEBUG (csh ex: setenv CPPFLAGS -DNDEBUG).

Variable Description Notes

CC C compiler If you don’t specify this, the configure script will try
to find a suitable C compiler such as cc, c89, xlc, or
gcc.

FC Fortran If you don’t specify this, the configure script will try
compiler (if to find a suitable Fortran 90 or Fortran 77 compiler.
any) Set FC to "" explicitly, if no Fortran interface is
desired.

F90 Fortran 90 If you don’t specify this, the configure script will try
compiler (if to find a suitable Fortran 90 compiler. Not needed
any) if FC specifies a Fortran 90 compiler. Set F90 to
"" explicitly, if no Fortran 90 interface desired. For
a vendor F90 compiler, make sure you’re using the
same vendor’s F77 compiler. Using Fortran compil-
ers from different vendors, or mixing vendor com-
pilers with g77, the GNU F77 compiler, is not sup-
ported and may not work.
Chapter 3: Building and Installing NetCDF on Unix Systems 7

CXX C++ compiler If you don’t specify this, the configure script will
try to find a suitable C++ compiler. Set CXX to ""
explicitly, if no C++ interface is desired. If using a
vendor C++ compiler, use that vendor’s C compiler
to compile the C interface. Using different vendor
compilers for C and C++ may not work.

CFLAGS C compiler "-O" or "-g", for example.

flags
CPPFLAGS C preprocessor "-DNDEBUG" to omit assertion checks, for exam-
options ple.

FFLAGS Fortran "-O" or "-g", for example.

compiler flags
F90FLAGS Fortran 90 "-O" or "-g", for example. If you don’t specify this,
compiler flags the value of FFLAGS will be used.

CXXFLAGS C++ compiler "-O" or "-g", for example.

flags
ARFLAGS, Miscellaneous One or more of these were needed for some platforms,
NMFLAGS, as specified below. Unless specified, you should not
FPP, M4FLAGS, set these environment variables, because that may
LIBS, FLIBS, interfere with the configure script.
FLDFLAGS
The section marked Tested Systems below contains a list of systems on which we have
built this package, the environment variable settings we used, and additional commentary.

3.3 Building on 64 Bit Platforms

Some platforms support special options to build in 64-bit mode.
NetCDF 3.6.1 has been tested as 64-bit builds on SunOS, Irix, and AIX. The options
needed to build in 64-bit mode on these platforms are described here, and can be turned
on by providing the –enable-64bit flag to configure.

AIX Set -q64 option in all compilers, and set NMFLAGS to -X64, and ARFLAGS
to ’-X64 cru’. Alternatively, set environment variable OBJECT MODE to 64
before running configure.

IRIX Set the -64 option in all compilers.

SunOS Use the -xarch=v9 flag on all compilers. This is not supported on the x86
platform.

3.4 Running the configure Script

To create the Makefiles needed to build netCDF, you must run the provided configure script.
Go to the top-level netCDF src/ directory.
8 NetCDF Installation and Porting Guide

Decide where you want to install this package. Use this for the "–prefix=" argument
to the configure script below. The default installation prefix is "..", which will install the
package’s files in ../bin, ../lib, and ../man relative to the netCDF src/ directory.
Execute the configure script:
./configure --prefix=whatever_you_decided
The "–prefix=..." specification is optional; if omitted, ".." designating the parent direc-
tory will be used as a default. There are other options for the configure script. The most
useful ones are listed below. Use the –help option to get the full list.
--prefix Specify the directory under which netCDF will be installed. Directories lib and
bin will be created, as well as some others. The default value for prefix is one
directory up from the src directory, where the build takes place.
--disable-flag-setting
By default the configure script changes some compiler flags to allow netCDF
to build on your platform. If you wish to specify compiler flags which conflict
with the ones added by the configure script, then use this option to instruct
configure not to attempt to set any compiler flags. It is then the responsibility
of the user to correctly set CPPFLAGS, CFLAGS, etc. (Note that this flag
does not affect some setting of flags by configure for GNU platforms; it just
turns off any special netCDF flags.
--enable-64bit
Compile for 64-bit platform on Sun, AIX, HPUX, or Irix. (Has no effect on
other platforms). Since this works by setting some compiler flags, this option
is incompatible with –disable-flag-setting.
The configure script will examine your computer system – checking for attributes that
are relevant to building the netCDF package. It will print to standard output the checks
that it makes and the results that it finds.
The configure script will also create the file "config.log", which will contain error mes-
sages from the utilities that the configure script uses in examining the attributes of your
system. Because such an examination can result in errors, it is expected that "config.log"
will contain error messages. Therefore, such messages do not necessarily indicate a problem
(a better indicator would be failure of the subsequent "make"). One exception, however, is
an error message in "config.log" that indicates that a compiler could not be started. This
indicates a severe problem in your compilation environment – one that you must fix.

3.5 Running make

Run "make". This will build one or more netCDF libraries. It will build the basic netCDF
library libsrc/libnetcdf.a. If you have Fortran 77 or Fortran 90 compilers, then the Fortran
interfaces will be included in this library. If you have a C++ compiler, then the C++ interface
will be built into the library cxx/libnetcdf c++.a. This will also build the netCDF utilities
ncgen(1) and ncdump(1).
Run make like this:
make
Chapter 3: Building and Installing NetCDF on Unix Systems 9

3.6 Testing the Build

Run “make check” to verify that the netCDF library and executables have been built
properly (you can instead run “make test” which does the same thing).
A make check will build and run various test programs that test the C, Fortran, and
C++ interfaces as well as the "ncdump" and "ncgen" utility programs.
Lines in the output beginning with "***" report on success or failure of the tests; any
failures will be reported before halting the test. Compiler and linker warnings during the
testing may be ignored.
Run the tests like this:
make check
If you plan to use the 64-bit offset format (introduced in version 3.6.0) to create very
large files (i.e. larger than 2 GB), you should probably run “make extra check which tests
the large file features. You must have 13 GB of free disk space for these tests to successfully
run.
If you are running make extra check, you may wish to override the make file variable
TEMP LARGE to specify a directory to which large files can be written. The default is to
create them in the nc test subdirectory of the netCDF build.
Run the large file tests like this:
make extra_check
Or, to specify a directory where the large files should be written during the tests (the
example below uses the /tmp directory):
make TEMP_LARGE=/tmp extra_check
If you have an environment variable TEMP LARGE, the configure script will tell the
makefile to use that directory for large files.
All of the large files are removed on successful completion of tests. If the test fails, you
may wish to make sure that no large files have been left around.
If any of the the large file tests test fail, run make check to run additional large file tests,
including a test which uses the dd command to ensure that your file system can handle files
larger than 2 GiB. This test runs the command:
dd if=/dev/zero bs=1000000 count=3000 of=$(TEMP_LARGE)/largefile
If your system does not have a /dev/zero, this test will fail. If all other tests pass, this
is if no concern, but if other tests fail, you need to somehow ensure that your file system
can handle very large files.
These tests are slower; to run the slow large file tests:
make slow_check
This file system test can also be run by going into the directory nc test and making
the target lfs test. The target slow check runs an additional large file test, which writes
about 4GiB of data to a file, and then rereads it. Also in the nc test directory, the target
all large tests will run all the large file tests.
See Chapter 5 [If Something Goes Wrong], page 21.
10 NetCDF Installation and Porting Guide

3.7 Installing NetCDF

To install the libraries and executables, run "make install". This will install to the directory
specified in the configure step, or to ../lib (that is, it will create a lib directory under the
netcdf-3.6.1 directory, and install the library there.)
Run the installation like this:
make install
Try linking your applications. Let us know if you have problems (see Section 5.4 [Re-
porting Problems], page 24). Port the library to other platforms. Share data.

3.8 Platform Specific Notes

The following platform-specific note may be helpful when building and installing netCDF.
Consult your vendor manuals for information about the options listed here. Compilers can
change from version to version; the following information may not apply to your platform.
Full output from some of the platforms of the test platforms for netCDF 3.6.1 can be
found at http://www.unidata.ucar.edu/software/netcdf/builds.

3.8.1 AIX
We found the vendor compilers in /usr/vac/bin, and included this in our PATH. Compilers
were xlc, xlf, xlf90, xlC.
The F90 compiler requires the qsuffix option to believe that F90 code files can end with
.f90. This is automatically turned on by configure when needed (we hope):
F90FLAGS=-qsuffix=f=f90
We had to use xlf for F77 code, and xlf90 for F90 code.
To compile 64-bit code, use the –enable-64bit option when running configure, and it will
set the appropriate environment variables for you (documented below).
The environment variable OBJECT MODE can be set to 64, or use the -q64 option on
all AIX compilers by setting CFLAGS, FFLAGS, and CXXFLAGS to -q64.
The following is also necessary on an IBM AIX SP system for 64-bit mode:
ARFLAGS=’-X64 cru’
NMFLAGS=’-X64’
There are thread-safe versions of the AIX compilers. For example, xlc r is the thread-
safe C compiler. The NetCDF configure script ignores these compilers. To use thread-safe
compilers, override the configure script by setting CC to xlc r; similarly for FC and CXX.
For large file support, AIX requires that the macro LARGE FILES be defined. The
configure script does this using AC SYS LARGEFILES. Unfortunately, this misfires when
OBJECT MODE is 64, or the q64 option is used. The netCDF tries to fix this by turning
on LARGE FILES anyway in these cases.
The GNU C compiler does not mix successfully with the AIX fortran compilers.

3.8.2 Cygwin
NetCDF builds under Cygwin tools on Windows just as with Linux.
Chapter 3: Building and Installing NetCDF on Unix Systems 11

3.8.3 HPUX
The HP Fortran compiler (f77, a.k.a. fort77, also f90) requires FLIBS to include -lU77 for
the fortran tests to work. The configure script does this automatically.
For the c89 compiler to work, CPPFLAGS must include -D HPUX SOURCE. This isn’t
required for the cc compiler. The configure script adds this as necessary.
For large file support, HP-UX requires FILE OFFSET BITS=64. The configure script
sets this automatically.
The HPUX C++ compiler doesn’t work on netCDF code. It’s too old for that. So either
use GNU to compile netCDF, or skip the C++ code by setting CXX to ” (in csh: setenv
CXX ”).
Building a 64 bit version may be possible with the following settings:
CC=/bin/cc
CPPFLAGS=’-D_HPUX_SOURCE -D_FILE_OFFSET_BITS=64’ # large file support
CFLAGS=’-g +DD64’ # 64-bit mode
FC=/opt/fortran90/bin/f90 # Fortran-90 compiler
FFLAGS=’-w +noppu +DA2.0W’ # 64-bit mode, no "_" suffixes
FLIBS=-lU77
CXX=’’ # no 64-bit mode C++ compiler
Sometimes quotas or configuration causes HPUX disks to be limited to 2 GiB files. In
this cases, netCDF cannot create very large files. Rather confusingly, HPUX returns a
system error that indicates that a value is too large to be stored in a type. This may
cause scientists to earnestly check for attempts to write floats or doubles that are too large.
In fact, the problem seems to be an internal integer problem, when the netCDF library
attempts to read beyond the 2 GiB boundary. To add to the confusion, the boundary for
netCDF is slightly less than 2 GiB, since netCDF uses buffered I/O to improve performance.

3.8.4 Irix
A 64-bit version can be built with the –enable-64bit option when running configure; it will
set the appropriate environment variables for you.
It builds 64-bit by setting CFLAGS, FFLAGS, and CXXFLAGS to -64.
On our machine, there is a /bin/cc and a /usr/bin/cc, and the -64 option only works
with the former.

3.8.5 Linux
The f2cFortran flag is required with GNU fortran:
CPPFLAGS=-Df2cFortran
For Portland Group Fortran, set pgiFortran instead:
CPPFLAGS=-DpgiFortran
Portland Group F90/F95 does not mix with GNU g77.
The netCDF configure script should notice which fortran compiler is being used, and set
these automatically.
For large file support, FILE OFFSET BITS must be set to 64. The netCDF configure
script should set this automatically.
12 NetCDF Installation and Porting Guide

3.8.6 Macintosh
The f2cFortran flag is required with GNU fortran (CPPFLAGS=-Df2cFortran). The
NetCDF configure script should and set this automatically.
For IBM compilers on the Mac, the following may work (we lack this test environment):
CC=/usr/bin/cc
CPPFLAGS=-DIBMR2Fortran
FC=xlf
F90=xlf90
F90FLAGS=-qsuffix=cpp=f90

3.8.7 OSF1
NetCDF builds out of the box on OSF1.

3.8.8 SunOS
PATH should contain /usr/ccs/bin to find make, nm, ar, etc.
For large file support, FILE OFFSET BITS must be 64. Configure will turn this on
automatically.
Large file support doesn’t work with c89, unless the -Xa option is used. The netCDF
configure script turns this on automatically where appropriate.
To compile in 64-bit mode, use option –enable-64bit with configure. It sets -xarch=v9
on all compilers (i.e. in CFLAGS, FFLAGS, and CXXFLAGS).
When compiling with GNU Fortran (g77), the -Df2cFortran flag is required for the
Fortran interface to work. The NetCDF configure script turns this on automatically if
needed.

3.8.9 Handling Fortran Compilers

Commercial fortran compilers will generally require at least one flag in the CPPFLAGS
veriable. The netCDF configure script tries to set this for you, but won’t try if you have
used –disable-flag-setting, or if you have already set CPPFLAGS, CFLAGS, CXXFLAGS,
FCFLAGS, or F90FLAGS yourself.
The first thing to try is to set nothing and see if the netCDF configure script finds your
fortran compiler, and sets the correct flags automatically.
If it doesn’t find the correct fortran compiler, you can next try setting the FC environ-
ment variable to the compiler you wish to use, and then see if the configure script can set
the correct flags for that compiler.
If all that fails, you must set the flags yourself.
The intel compiler likes the pgiFortran flag, as does the Portland Group compiler. (Au-
tomatically turned on if your fortran compiler is named “ifort” or “pgf90”).

3.9 Additional Porting Notes

The configure and build system should work on any system which has a modern "sh" shell,
"make", and so on. The configure and build system is less portable than the "C" code
itself, however. You may run into problems with the "include" syntax in the Makefiles.
Chapter 3: Building and Installing NetCDF on Unix Systems 13

You can use GNU make to overcome this, or simply manually include the specified files
after running configure.
Instruction for building netCDF on other platforms can be found at
http://www.unidata.ucar.edu/software/netcdf/other-builds.html. If you
build netCDF on a new platform, please send your environment variables and any other
important notes to [email protected] and we will add the information to the other
builds page, with a credit to you.
If you can’t run the configure script, you will need to create libsrc/ncconfig.h and for-
tran/nfconfig.inc. Start with libsrc/ncconfig.in and fortran/nfconfig.in and set the defines
as appropriate for your system.
Operating system dependency is isolated in the "ncio" module. We provide two versions.
posixio.c uses POSIX system calls like "open()", "read()" and "write(). ffio.c uses a special
library available on CRAY systems. You could create other versions for different operating
systems. The program "t ncio.c" can be used as a simple test of this layer.
Note that we have not had a Cray to test on for some time. In particular, large file
support is not tested with ffio.c.
Numerical representation dependency is isolated in the "ncx" module. As supplied,
ncx.m4 (ncx.c) supports IEEE floating point representation, VAX floating point, and CRAY
floating point. BIG ENDIAN vs LITTLE ENDIAN is handled, as well as various sizes of
"int", "short", and "long". We assume, however, that a "char" is eight bits.
There is a separate implementation of the ncx interface available as ncx cray.c which
contains optimizations for CRAY vector architectures. Move the generic ncx.c out of the
way and rename ncx cray.c to ncx.c to use this module. By default, this module does not
use the IEG2CRAY and CRAY2IEG library calls. When compiled with aggressive in-lining
and optimization, it provides equivalent functionality with comparable speed and clearer
error semantics. If you wish to use the IEG library functions, compile this module with
-DUSE IEG.
14 NetCDF Installation and Porting Guide
Chapter 4: Building and Installing NetCDF on Windows 15

4 Building and Installing NetCDF on Windows

NetCDF can be built and used from a variety of development environments on Windows.
The netCDF library is implemented as a Windows dynamic link library (DLL). The simplest
way to get started with netCDF under Windows is to download the pre-built DLL from the
Unidata web site.
Building under the Cygwin port of GNU tools is treated as a Unix install. See Section 3.8
[Platform Specific Notes], page 10.
Instructions are also given for building the netCDF DLL from the source code.
VC++ documentation being so voluminous, finding the right information can be a chore.
There’s a good discussion of using DLLs called “About Dynamic-Link Libraries” at (per-
haps) http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dllproc/base/dynamic_
link_libraries.asp.
From the .NET point of view, the netCDF dll is unmanaged code. As a starting point,
see the help topic “Consuming Unmanaged DLL Functions” which may be found at
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/html/cpconConsuming
unless the page has been moved.

4.1 Getting Prebuilt netcdf.dll

We have pre-built Win32 binary versions of the netcdf dll and static library, as
well as ncgen.exe and ncdump.exe (dll and static versions). You can get them from
ftp://ftp.unidata.ucar.edu/pub/netcdf/contrib/win32netcdf-3.6.1-beta1-win32dll.zip.
(Note: we don’t have a C++ interface here).

4.2 Installing the DLL

Whether you get the pre-built DLL or build your own, you’ll then have to install it some-
where so that your other programs can find it and use it.
To install a DLL, you just have to leave it in some directory, and (possibly) tell your
compiler what directory to look for it in.
A DLL is a library, and functions just like libraries under the Unix operating system.
As with any library, the point of the netCDF DLL is to provide functions that you can call
from your own code. When you compile that code, the linker needs to be able to find the
library, and then it pulls out the functions that it needs. In the Unix world, the -L option
tells the compiler where to look for a library. In Windows, library search directories can be
added to the project’s property dialog.
Similarly, you will need to put the header file, netcdf.h, somewhere that you compiler
can find it. In the Unix world, the -I option tells the compiler to look in a certain directory
to find header files. In the Windows world, you set this in the project properties dialog box
of your integrated development environment.
Therefore, installing the library means nothing more than copying the DLL somewhere
that your compiler can find it, and telling the compiler where to look for them.
The standard place to put DLLs is Windows\System32 folder (for Windows2000/XP)
or the Windows\System folder (for Windows 98/ME). If you put the DLL there, along with
16 NetCDF Installation and Porting Guide

the ncgen and ncdump executables, you will be able to use the DLL and utilities without
further work, because compilers already look there for DLLs and EXEs.
Instead of putting the DLL and EXEs into the system directory, you can leave them
wherever you want, and every development project that uses the dll will have to be told
to search the netCDF directory when it’s linking, or, the chosen directory can be added to
your path.
On the .NET platform, you can also try to use the global assembly cache. (To learn
how, see MSDN topic “Global Assembly Cache”, at www.msdn.microsoft.com).
Following Windows conventions, the netCDF files belong in the following places:

File(s) Description Location

netcdf.dll C and Fortran function in DLL Windows\System

(98/ME) or
Windows\System32
(2000/XP)

netcdf.lib Library file Windows\System

(98/ME) or
Windows\System32
(2000/XP)

ncgen.exe, NetCDF utilities Windows\System

ncdump.exe (98/ME) or
Windows\System32
(2000/XP)

netcdf-3\src netCDF source code Program

Files\Unidata

4.3 Building netcdf.dll with VC++ 6.0

The most recent releases of netCDF aren’t tested under VC++ 6.0. (They are tested with
VC++.NET). Older versions of the library, notably 3.5.0, did compile with VC++ 6.0, and
the instructions for doing so are presented below.
Note that the introduction of better large file support (for files larger than 2 GiB) in
version 3.6.0 and greater requires an off t type of 8 bytes, and it’s not clear how, or if, this
can be found in VC++ 6.0.
To build the library yourself, get the file ftp://ftp.unidata.ucar.edu/pub/netcdf/contrib/win32netcdf-
3.5.0.win32make.VC6.zip
The makefiles there describe how to build netcdf-3.5 using the using Microsoft Visual C++
6.x and (optionally) Digital Visual Fortran 6.x. Because of difficulties in getting Microsoft
Visual Studio to fall in line with our existing source directory scheme, we chose not to
build the system "inside" Visual Studio. Instead, we provide a simple group of "msoft.mak"
Chapter 4: Building and Installing NetCDF on Windows 17

files which can be used. If you wish to work in Visual Studio, go ahead. Read the section
called "Macros" at the end of this discussion.
As of this writing, we have not tried compiling the C++ interface in this environment.
nmake is a Microsoft version of make, which comes with VC 6.0 (and VC 7.0) in di-
rectory C:\Program Files\Microsoft Visual Studio\VC98\Bin (or, for VC 7.0, C:\Program
Files\Microsoft Visual Studio .NET 2003\Vc7\bin).
To build netcdf, proceed as follows:
unpack source distribution.
copy netcdf-3.5.0.win32make.VC6.zip
copy netcdf-3.5.0.win32make.VC6.zip into the netcdf-3.5.0/src directory, and
unzip it from there.
cd src\libsrc; nmake /f msoft.mak
Run this command in src\libsrc. This will build netcdf.lib and netcdf.dll Note:
This makefiles make DLLs. To make static libraries see section on static li-
braries.
nmake /f msoft.mak test
Optionally, in src\libsrc, make and run the simple test.
cd ..\fortran; nmake /f msoft.mak
Optionally build the fortran interface and rebuild dll in ..\libsrc to include the
fortran interface. Note Bene: We don’t provide a .DEF file, so this step changes
the "ordinals" by which entry points in the DLL found. Some sites may wish
to modify the msoft.mak file(s) to produce a separate library for the fortran
interface.
nmake /f msoft.mak test
(necessary if you want to use fortran code) While you are in src\fortran; nmake
/f msoft.mak test This tests the netcdf-2 fortran interface.
cd ..\nctest; nmake /f msoft.mak test
(optional, but recommended) In src\nctest; nmake /f msoft.mak test This tests
the netcdf-2 C interface.
cd ..\nc_test; nmake /f msoft.mak test
(optional, but highly recommended) In src\nc test; nmake /f msoft.mak test
This tortures the netcdf-3 C interface.
cd ..\nf_test; nmake /f msoft.mak test
(optional, but highly recommended if you built the fortran interface) In
src\nf test; nmake /f msoft.mak test This tortures the netcdf-3 fortran
interface.
..\ncdump; nmake /f msoft.mak
In src\ncdump; nmake /f msoft.mak This makes ncdump.exe.
..\ncgen; nmake /f msoft.mak
In src\ncgen; nmake /f msoft.mak This makes ncgen.exe.
18 NetCDF Installation and Porting Guide

..\ncdump; nmake /f msoft.mak test

(optional) In src\ncdump; nmake /f msoft.mak test This tests ncdump. Both
ncgen and ncdump need to be built prior to this test. Note the makefile sets
the path so that ..\libsrc\netcdf.dll can be located.

..\ncgen; nmake /f msoft.mak test

(optional) In src\ncgen; nmake /f msoft.mak test This tests ncgen. Both ncgen
and ncdump need to be built prior to this test. Note the makefile sets the path
so that ..\libsrc\netcdf.dll can be located.

To Install
Copy libsrc\netcdf.lib to a LIBRARY directory. Copy libsrc\netcdf.h
and fortran/netcdf.inc to an INCLUDE directory. Copy libsrc\netcdf.dll,
ncdump/ncdump.exe, and ncgen/ncgen.exe to a BIN directory (someplace in
your PATH).

4.4 Using netcdf.dll with VC++ 6.0

To use the netcdf.dll:
1. Place these in your include directory: netcdf.h C include file netcdf.inc Fortran include
file
2a. To use the Dynamic Library (shared) version of the netcdf library: Place these in a
directory that’s in your PATH: netcdf.dll library dll ncgen.exe uses the dll ncdump.exe uses
the dll
Place this in a library directory to link against: netcdf.lib library
2b. Alternatively, to use a static version of the library
Place this in a library directory to link against: netcdfs.lib library
Place these in a directory that’s in your PATH: ncgens.exe statically linked (no DLL
needed) ncdumps.exe statically linked (no DLL needed)

4.5 Building netcdf.dll with VC++.NET

To build the netCDF dll with VC++.NET open the win32/NET/netcdf.sln file with Visual
Studio. Both Debug and Release configurations are available - select one and build.
The resulting netcdf.dll file will be in subdirectory Release or Debug.
The netCDF tests will be built and run as part of the build process. The Fortran 77
interface will be built, but not the Fortran 90 or C++ interfaces.
The quick large files test program is provided as an extra project, however it is not
run during the build process, but can be run from the command line or the IDE. Note
that, despite its name, it is not quick. On Unix systems, this program runs in a few
seconds, because of some features of the Unix file system apparently not present in Windows.
Nonetheless, the program does run, and creates (then deletes) some very large files. (So
make sure you have at least 15 GiB of space available). It takes about 45 minutes to run
this program on our Windows machines, so please be patient.
Chapter 4: Building and Installing NetCDF on Windows 19

4.6 Using netcdf.dll with VC++.NET

Load-time linking to the DLL is the most straightforward from C++. This means the
netcdf.lib file has to end up on the compile command line. This being Windows, that’s
hidden by a GUI.
In Visual Studio 2003 this can be done by modifying three of the project’s properties.
Open the project properties window from the project menu. Go to the linker folder and
look at the general properties. Modify the property “Additional Library Directories” by
adding the directory which contains the netcdf.dll and netcdf.lib files. Now go to the linker
input properties and set the property “Additional Dependencies” to netcdf.lib.
Finally, still within the project properties window, go to the C/C++ folder, and look at
the general properties. Modify “Additional Include Directories” to add the directory with
the netcdf.h file.
Now use the netCDF functions in your C++ code. Of course any C or C++ file that wants
to use the functions will need:
#include <netcdf.h>
20 NetCDF Installation and Porting Guide
Chapter 5: If Something Goes Wrong 21

5 If Something Goes Wrong

The netCDF package is designed to build and install on a wide variety of platforms, but
doesn’t always. It’s a crazy old world out there, after all.

5.1 The Usual Build Problems

5.1.1 Taking the Easy Way Out
Why not take the easy way out if you can?
Precompiled binaries for many platforms can be found at http://www.unidata.ucar.edu/software/netcdf
Click on your platform, and copy the files from the bin, include, lib, and man directories
into your own local equivalents (Perhaps /usr/local/bin, /usr/local/include, etc.).

5.1.2 How to Clean Up the Mess from a Failed Build

If you are trying to get the configure or build to work, make sure you start with a clean
distribution for each attempt. If netCDF failed in the “make” you must clean up the mess
before trying again. To clean up the distribution:
make distclean

5.1.3 Platforms On Which NetCDF is Known to Work

At NetCDF World Headquarters (in sunny Boulder, Colorado), as part of the wonderful
Unidata organization, we have a wide variety of computers, operating systems, and compil-
ers. At night, house elves test netCDF on all these systems.
Output for the netCDF test platforms can be found at http://www.unidata.ucar.edu/software/netcdf/b
Compare the output of your build attempt with ours. Are you using the same compiler?
The same flags? Look for the configure output that lists the settings of CC, FC, CXX,
CFLAGS, etc.
On some systems you have to set environment variables to get the configure and build
to work.
For example, for a 64-bit IRIX install of the netCDF-3.6.1 release, the variables are
set before netCDF is configured or built. In this case we set CFLAGS, CXXFLAGS,
and FFLAGS. (This can also be accomplished automatically by using –enable-64bit with
configure.)
flip% uname -a
IRIX64 flip 6.5 07080050 IP30 mips
flip% setenv CFLAGS -64
flip% setenv CXXFLAGS -64
flip% setenv FFLAGS -64
flip% make distclean;./configure;make extra_check

5.1.4 Platforms On Which NetCDF is Reported to Work

If your platform isn’t listed on the successful build page, see if another friendly
netCDF user has sent in values for environment variables that are reported to work:
(http://www.unidata.ucar.edu/software/netcdf/other-builds.html).
22 NetCDF Installation and Porting Guide

If you build on a system that we don’t have at Unidata (particularly if it’s something
interesting and exotic), please send us the settings that work (and the entire build output
would be nice too). Send them to [email protected].

5.1.5 If You Have a Broken Compiler

For netCDF to build correctly, you must be able to compile C from your environment, and,
optionally, Fortran 77, Fortran 90, and C++. If C doesn’t work, netCDF can’t compile.
What breaks a C compiler? Installation or upgrade mistakes when the C compiler was
installed, or multiple versions or compilers installed on top of each other. Commercial
compilers frequently require some environment variables to be set, and some directories to
appear ahead of others in your path. Finally, if you have an expired or broken license, your
C complier won’t work.
If you have a broken C compiler and a working C compiler in your PATH, netCDF
might only find the broken one. You can fix this by explicitly setting the CC environmental
variable to a working C compiler, and then trying to build netCDF again. (Don’t forget to
do a “make distclean” first!)
If you can’t build a C program, you can’t build netCDF. Sorry, but that’s just the way
it goes. (You can get the GNU C compiler - search the web for “gcc”).
If netCDF finds a broken Fortran 90, Fortran 77, or C++ compiler, it will report the
problem during the configure, and then drop the associated API. For example, if the C++
compiler can’t compile a very simple test program, it will drop the C++ interface. If you
really want the C++ API, set the CXX environment variable to a working C++ compiler.

5.1.6 What to Do If NetCDF Still Won’t Build

If none of the above help, try our troubleshooting section: See Section 5.2 [Troubleshooting],
page 22.
Also check to see of your problem has already been solved by someone else (see Section 5.3
[Finding Help], page 23).
If you still can’t get netCDF to build, report your problem to Unidata, but please make
sure you submit all the information we need to help (see Section 5.4 [Reporting Problems],
page 24).

5.2 Troubleshooting
5.2.1 Problems During Configuration
If the ./configure; make check fails, it’s a good idea to turn off the C++ and Fortran inter-
faces, and try to build the C interface alone. All other interfaces depend on the C interface,
so nothing else will work until the C interface works. To turn off C++ and Fortran, set
environment variables CXX and FC to NULL before running the netCDF configure script
(with csh: setenv FC ”;setenv CXX ”).
Turning off the Fortran and C++ interfaces results in a much shorter build and test cycle,
which is useful for debugging problems.
If the netCDF configure fails, most likely the problem is with your development envi-
ronment. The configure script looks through your path to find all the tools it needs to
Chapter 5: If Something Goes Wrong 23

build netCDF, including C compiler and linker, the ar, ranlib, and others. The configure
script will tell you what tools it found, and where they are on your system. Here’s part of
configure’s output on a Linux machine:
checking CPPFLAGS... -Df2cFortran
checking CC CFLAGS... cc -g
checking which cc... /usr/bin/cc
checking CXX... c++
checking CXXFLAGS... -g -O2
checking which c++... /usr/local/bin/c++
checking FC... f77
checking FFLAGS...
checking which f77... /usr/bin/f77
checking F90... unset
checking AR... ar
checking ARFLAGS... cru
checking which ar... /usr/bin/ar
checking NM... nm
checking NMFLAGS...
checking which nm... /usr/bin/nm
Make sure that the tools, directories, and flags are set to reasonable values, and com-
patible tools. For example the GNU tools may not inter-operate well with vendor tools. If
you’re using a vendor compiler, use the ar, nm, and ranlib that the vendor supplied.
As configure runs, it creates a config.log file. If configure crashes, do a text search
of config.log for thing it was checking before crashing. If you have a licensing or tool
compatibility problem, it will be obvious in config.log.

5.2.2 Problems During Compilation

If the configure script runs, but the compile step doesn’t work, or the tests don’t complete
successfully, the problem is probably in your CFLAGS or CPPFLAGS.

5.2.3 Problems During Testing

If you are planning on using large files (i.e. > 2 GiB), then make sure you run “make
extra check to ensure that large files work on your system. Run this in addition to “make
check.
If any of the tests in “make extra check fail, before reporting a problem, run “make
slow check” to run additional large file tests, including one that will check your file system
for large files.

5.3 Finding Help On-line

The latest netCDF documentation (including this manual) can be found at
http://www.unidata.ucar.edu/software/netcdf/docs.
The output of successful build and test runs for recent versions of netCDF can be found
at http://www.unidata.ucar.edu/software/netcdf/builds.
A list of known problems with netCDF builds, and suggested fixes, can be found at
http://www.unidata.ucar.edu/software/netcdf/docs/known_problems.html.
24 NetCDF Installation and Porting Guide

Reportedly successful settings for platforms unavailable for netCDF testing can be found
at http://www.unidata.ucar.edu/software/netcdf/other-builds.html. If you build
netCDF on a system that is not listed, please send your environment settings, and the full
output of your configure, compile, and testing, to [email protected]. We will add
the information to the other-builds page, with a credit to you.
The replies to all netCDF support emails are on-line and can be searched. Before re-
porting a problem to Unidata, please search this on-line database to see if your problem has
already been addressed in a support email. If you are having build problems it’s usually
useful to search on your system host name. On Unix systems, use the uname command to
find it.
The netCDF Frequently Asked Questions (FAQ) list can be found at
http://www.unidata.ucar.edu/software/netcdf/faq.html.
To search the support database, see http://www.unidata.ucar.edu/mailsearchform.php?archive=netcd
The netCDF mailing list also can be searched; see http://www.unidata.ucar.edu/mailsearchform.php?a

5.4 Reporting Problems

To help us solve your problem, please include the following information in your email to
[email protected].
Unfortunately, we can’t solve build questions without this information; if you ask for
help without providing it, we’re just going to have to ask for it.
So why not send it immediately, and save us both the extra trouble?
1. the exact version of netCDF - see the src/VERSION file.
2. the *complete* output of “./configure”, “make”, and “make check. Yes, it’s long, but
it’s all important.
3. if the configure failed, the contents of config.log.
4. if you are having problems with very large files (larger than 2GiB), the output of “make
check”.
Although responses to your email will be available in our support database, your email
address is not included, to provide spammers with one less place to harvest it from.
Index 25

Index

G
LARGE FILES, on AIX . . . . . . . . . . . . . . . . . . . . . 10 GNU make . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

6 H
64-bit platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 HPUX, building on . . . . . . . . . . . . . . . . . . . . . . . . . . 10

A I
install directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
AIX 64-bit build . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 installation requirements . . . . . . . . . . . . . . . . . . . . . . 5
AIX, building on . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 installing binary distribution . . . . . . . . . . . . . . . . . . . 1
ar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 installing netCDF. . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
autoconf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Intel fortran . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Irix, building on . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
B
big endian. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 K
binaries, windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 known problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
binary install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
binary releases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
bugs, reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 L
large file tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
large file tests requirements . . . . . . . . . . . . . . . . . . . . 5
C large file tests, for windows . . . . . . . . . . . . . . . . . . . 18
config.log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Linux, building on . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
configure, running . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 little endian . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
CRAY, porting to . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Cygwin, building with . . . . . . . . . . . . . . . . . . . . . . . . 10
M
m4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
D Macintosh, building on . . . . . . . . . . . . . . . . . . . . . . . 10
mailing lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
debug directory, windows . . . . . . . . . . . . . . . . . . . . . 18 make all large tests . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
DLL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 make check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
dll, getting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 make extra check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 make extra test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
documents, latest version . . . . . . . . . . . . . . . . . . . . . . 5 make install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
make lfs test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
make slow check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
E make test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
earlier netCDF versions . . . . . . . . . . . . . . . . . . . . . . . 5 make, running . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
extra check requirements . . . . . . . . . . . . . . . . . . . . . . 5 makeinfo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
extra test requirements. . . . . . . . . . . . . . . . . . . . . . . . 5 Microsoft . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

F N
ncconfig.h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
FAQ for netCDF . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 ncconfig.in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
ffio.c . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 ncconfig.inc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
flex and yacc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 ncdump, windows location . . . . . . . . . . . . . . . . . . . . 15
fortran, Intel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 ncgen, windows location . . . . . . . . . . . . . . . . . . . . . . 15
fortran, Portland Group . . . . . . . . . . . . . . . . . . . . . . 10 ncio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
ncx.m4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
26 NetCDF Installation and Porting Guide

NET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 S
netcdf.dll, location . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 successful build output, on web . . . . . . . . . . . . . . . 23
netcdf.lib. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 SunOS 64-bit build . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
nm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
SunOS, building on . . . . . . . . . . . . . . . . . . . . . . . . . . 10
support email . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
O
OBJECT MODE, on AIX . . . . . . . . . . . . . . . . . . . . 10 T
OSF1, building on . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
other builds document . . . . . . . . . . . . . . . . . . . . . . . 23 TEMP LARGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
testing large file features . . . . . . . . . . . . . . . . . . . . . . 9
testing, for windows . . . . . . . . . . . . . . . . . . . . . . . . . . 18
P tests, running. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
porting notes, additional . . . . . . . . . . . . . . . . . . . . . 12 troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Portland Group fortran . . . . . . . . . . . . . . . . . . . . . . 10 turning off C++, Fortran interface . . . . . . . . . . . . . 22
posixio.c . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
prefix argument of configure . . . . . . . . . . . . . . . . . . . 7
problems, reporting . . . . . . . . . . . . . . . . . . . . . . . . . . 24 V
VC++ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
VC++ 6.0, building with . . . . . . . . . . . . . . . . . . . . . . 16
Q VC++ 6.0, using netcdf with . . . . . . . . . . . . . . . . . . 18
quick unix instructions . . . . . . . . . . . . . . . . . . . . . . . . 3 VC++.NET, building with . . . . . . . . . . . . . . . . . . . . 18
quick large files, in VC++.NET . . . . . . . . . . . . . . . 18 VC++.NET, using netcdf with . . . . . . . . . . . . . . . . 19
visual studio 2003 properties . . . . . . . . . . . . . . . . . . 19
R
release directory, windows . . . . . . . . . . . . . . . . . . . . 18 W
reporting problems . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 windows large file tests . . . . . . . . . . . . . . . . . . . . . . . 18
running configure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 windows testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
running make. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 windows, building on . . . . . . . . . . . . . . . . . . . . . . . . . 15