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.
>To: address@hidden >From: Arthur Snoke <address@hidden> >Subject: building problem >Organization: . >Keywords: 199706241312.HAA26722 Hi Arthur, Sorry this reply took so long. Your question was mistakenly sent to me when I was away from my email for a week. > I include below a log of my unsuccessful attempt to build netcdf v3.3.1. > > I am using a sun ultrasparc 140 running solaris2.5.1. I have installed > gcc but no other compilers. I do not actually have the libraries installed > for gc++. > > As you can see, everything appeared to go fine until it went into > subdirectory cxx. It seemed unable to find some include files, like > generic.h. Yet they are there is ~/src/ncgen. ... > Making `all' in directory /opt/GMT3.0/netcdf-3.3.1/src/cxx > > gcc -c -O -I../libsrc -DNDEBUG netcdf.cc > In file included from netcdf.hh:16, > from netcdf.cc:12: > ncvalues.hh:13: generic.h: No such file or directory > ncvalues.hh:14: iostream.h: No such file or directory > ncvalues.hh:18: strstream.h: No such file or directory This means g++ is unable to locate some standard include files that should be installed with any C++ compilation system. From the above, your g++ compiler probably won't even be able to compile the following standard 2-line program: #include <iostream.h> main() {cout << "Hello, world\n"; } You can either find out what's needed to get the g++ compiler to compile and link the above program first (probably just installing libg++ and the associated include files in a place where g++ can find them) or just disable the compilation and testing of the netCDF C++ interface by setting the environment variable CXX="" before invoking the configure script (after removing config.cache and running "make clean"). The C and Fortran part of the library will still work fine without the C++ interface. --Russ _____________________________________________________________________ Russ Rew UCAR Unidata Program address@hidden http://www.unidata.ucar.edu