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.
Francisco, > To: address@hidden > From: "Francisco Pagan" <address@hidden> > Subject: NetCDF Installation > Organization: University of Puerto Rico-Mayaguez > Keywords: 200405262043.i4QKhutK009323 netCDF Linux The above message contained the following: > I am trying to install NetCDF in a Microway AMD Opteron Beowulf > cluster (4 nodes) in the master (double processor). Here is the relevant > information, configuration as stated in your Others builds of the netcdf > package page). > > > Configuration: > CC=/usr/bin/gcc ; export CC > FC=/usr/pgi/linux86-64/5.1/bin/pgf77 ; export FC > CXX=/usr/bin/g++ ; export CXX > CFLAGS='-O3 -funroll-loops -m64 -mfpmath=sse -msse2 -ffast-math > -mcmodel=medium' ; export CFLAGS > CPPFLAGS='-DNDEBUG -Df2cFortran > -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE' ; export CPPFLAGS > FFLAGS='-fastsse -tp k8-64 -Minline > -Mvect=recog,transform,assoc,cachesize:1048576 -mcmodel=medium' ; export > FFLAGS > CXXFLAGS='-O3 -funroll-loops -m64 -mfpmath=sse -msse2 > -ffast-math -mcmodel=medium' ; export CXXFLAGS > > uname -a > Linux master 2.4.21-osmp #12 SMP Thu Aug 28 20:14:03 PDT 2003 x86_64 unknown > > VERSION > 3.5.1-beta13 > > macros.make > "empty" > > configure.log > creating cache ./config.cache > checking for top-level source-directory > /usr/lib_install/netcdf-3.5.1-beta13/src > checking for m4 preprocessor > checking for m4... m4 > checking m4 flags... -B10000 > checking C compiler "/usr/bin/gcc"... failed to compile test program The last line above indicates a severe problem with your C compilation environment. The reason can be found in your "config.log" file: > configure:1085: checking C compiler "/usr/bin/gcc" > configure:1094: /usr/bin/gcc -c -O3 -funroll-loops -march=k8 -m64 > -mfpmath=sse -msse2 -ffast-math -mcmodel=medium -DNDEBUG -Df2cFortran > -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE conftest.c 1>&5 > cc1: bad value (k8) for -march= switch > cc1: bad value (k8) for -mcpu= switch Apparently, the "-march=k8" option is illegal. Given that you specified the CFLAGS environment variable as > CFLAGS='-O3 -funroll-loops -m64 -mfpmath=sse -msse2 -ffast-math > -mcmodel=medium' ; export CFLAGS It seems likely that the CFLAGS variables was not correctly made an environment variable. A similar problem exists with your Fortran compiler: > checking user-defined Fortran-77 compiler "/usr/bin/g77"... failed to compile > test program For which the problem is also explained in your "config.log" file: > configure:1383: checking user-defined Fortran-77 compiler "/usr/bin/g77" > configure:1389: /usr/bin/g77 -c -O3 -funroll-loops -march=k8 -m64 > -mfpmath=sse -msse2 -ffast-math -mcmodel=medium -Wno-globals conftest.f > ./configure: line 1: /usr/bin/g77: No such file or directory Given that you specified the Fortran-77 compiler as > FC=/usr/pgi/linux86-64/5.1/bin/pgf77 ; export FC it seems likely that the FC variable was not correctly made an environment variable. Please do a "make distclean" and retry the build with the environment variables settings that you used before. before (re)executing the "configure" script, verify the settings with the following commands: env | grep CFLAGS env | grep FC Regards, Steve Emmerson