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.
Unidata Support <address@hidden> writes: > ------- Forwarded Message > >>To: address@hidden >>From: Jordan Dawe <address@hidden> >>Subject: netcdf cygwin build error, version 3.6.0-p1 >>Organization: UCAR/Unidata >>Keywords: 200505051800.j45I0iP3028282 > > I just tried to install netcdf onto the latest version of cygwin, and I > got a build error. Any advice? > ---------------------------- > netcdf version 3.6.0-p1 > > freedryk@jlaptop /usr/local/netcdf-3.6.0-p1/src > $ ./configure --prefix=/usr/local > checking build system type... i686-pc-cygwin > checking host system type... i686-pc-cygwin > checking for top-level source-directory... /usr/local/netcdf-3.6.0-p1/src > checking for gcc... gcc > checking whether we are using the GNU C compiler... no > checking whether gcc accepts -g... no > checking for gcc option to accept ANSI C... none needed > checking for g++... g++ > checking whether we are using the GNU C++ compiler... no > checking whether g++ accepts -g... no > checking C++ compiler "g++"... configure: WARNING: g++ failed on > standard C++ test program > checking for xlf... no > checking for f95... no > checking for fort... no > checking for xlf95... no > checking for ifc... no > checking for efc... no > checking for pgf95... no > checking for lf95... no > checking for gfortran... no > checking for frt... no > checking for pgf77... no > checking for f77... f77 > checking whether we are using the GNU Fortran compiler... no > checking whether f77 accepts -g... no > checking whether we are using the GNU Fortran compiler... (cached) no > checking whether f77 accepts -g... (cached) no > checking if Fortran-related pre-processor flag needed... > checking "f77" as Fortran-90 compiler... failed to build test program > checking for xlf90... no > checking for f90... no > checking for pgf90... no > checking for g95... no > configure: WARNING: "Could not find working Fortran-90 compiler" > configure: WARNING: "The Fortran-90 interface will not be built" > configure: checking for m4 preprocessor... > checking for m4... m4 > checking m4 flags... -B10000 > checking how to make dependencies... false > checking if we need to set _LARGE_FILES on AIX with OBJECT_MODE=64 or > CFLAGS includes -q64... > checking for special C compiler options needed for large files... no > checking for _FILE_OFFSET_BITS value needed for large files... no > checking for _LARGE_FILES value needed for large files... no > configure: checking for ar utility... > checking for ar... ar > checking ar flags... cru > configure: checking for nm utility... > checking for nm... nm > checking nm flags... > checking for ranlib... ranlib > checking for a BSD-compatible install... /usr/bin/install -c > checking CPPFLAGS... > checking CC CFLAGS... gcc -g > checking which gcc... /usr/bin/gcc > checking CXX... unset > 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 > checking RANLIB... ranlib > checking RANLIBFLAGS... > checking which ranlib... /usr/bin/ranlib > checking for SunOS Fortran -ftrap= option... > checking how to run the C preprocessor... gcc -E > checking user-defined Fortran-77 compiler "f77"... works > checking for Fortran .F compiler... > checking if Fortran-77 compiler handles *.F files... yes > checking for C-equivalent to Fortran routine "SUB"... sub_ > checking for Fortran "byte"... yes > checking for Fortran "integer*2"... yes > checking if Fortran "byte" is C "signed char"... yes > checking if Fortran "byte" is C "short"... no > checking if Fortran "byte" is C "int"... no > checking if Fortran "byte" is C "long"... no > checking if Fortran "integer*2" is C "short"... yes > checking if Fortran "integer*2" is C "int"... no > checking if Fortran "integer*2" is C "long"... no > checking if Fortran "integer" is C "int"... yes > checking if Fortran "real" is C "float"... yes > checking if Fortran "doubleprecision" is C "double"... yes > checking for Fortran-equivalent to netCDF "byte"... byte > checking for Fortran-equivalent to netCDF "short"... integer*2 > configure: checking for math library... > checking for tanh in -lc... yes > checking for egrep... grep -E > checking for ANSI C header files... no > checking for sys/types.h... no > checking for sys/stat.h... no > checking for stdlib.h... no > checking for string.h... no > checking for memory.h... no > checking for strings.h... no > checking for inttypes.h... no > checking for stdint.h... no > checking for unistd.h... no > checking for stdlib.h... (cached) no > checking for sys/types.h... (cached) no > checking for strerror... yes > checking for working ftruncate()... yes > checking for working alloca.h... yes > checking for alloca... yes > checking for struct stat.st_blksize... no > checking for IEEE floating point format... yes > checking for size_t... no > checking for off_t... no > checking for ssize_t... no > checking for ptrdiff_t... no > checking for uchar... no > checking whether char is unsigned... yes > checking whether byte ordering is bigendian... no > checking for short... no > checking size of short... 0 > checking for int... no > checking size of int... 0 > checking for long... no > checking size of long... 0 > checking for float... no > checking size of float... 0 > checking for double... no > checking size of double... 0 > checking size of off_t... 4 > checking size of size_t... 4 > checking for catman... no > checking for makewhatis... no > checking for /usr/lib/makewhatis... no > checking for manual-page index command... > checking binary distribution directory... /home/ftp/pub/binary/dummy_system > configure: creating ./config.status > config.status: creating macros.make > config.status: creating libsrc/ncconfig.h > config.status: libsrc/ncconfig.h is unchanged > config.status: creating fortran/nfconfig.inc > config.status: executing default commands > > freedryk@jlaptop /usr/local/netcdf-3.6.0-p1/src > $ make > make[1]: Entering directory `/usr/local/netcdf-3.6.0-p1/src' > > Making `all' in directory /usr/local/netcdf-3.6.0-p1/src/libsrc > > make[2]: Entering directory `/usr/local/netcdf-3.6.0-p1/src/libsrc' > gcc -c -g -I. attr.c > gcc -c -g -I. dim.c > gcc -c -g -I. error.c > gcc -c -g -I. -DVERSION=`cat ../VERSION` libvers.c > gcc -c -g -I. nc.c > gcc -c -g -I. ncio.c > gcc -c -g -I. ncx.c > ncx.c:1119:2: #error "ix_float implementation" > ncx.c:1542:2: #error "ix_double implementation" > make[2]: *** [ncx.o] Error 1 > make[2]: Leaving directory `/usr/local/netcdf-3.6.0-p1/src/libsrc' > make[1]: *** [subdir_target] Error 1 > make[1]: Leaving directory `/usr/local/netcdf-3.6.0-p1/src' > make: *** [libsrc/all] Error 2 > > > -- > NOTE: All email exchanges with Unidata User Support are recorded in the > Unidata inquiry tracking system and then made publicly available > through the web. If you do not want to have your interactions made > available in this way, you must let us know in each email you send to us. > > ------- End of Forwarded Message > > Sorry it's taken me so long to reply, but I was hoping to remember what that problem was, because I know I have encountered it before on cygwin. But when I do a build on cygwin, everything works fine with the latest netcdf tarball on the ftp site, on whichever machine I try. Do you have reasonably recent tools? I am using gcc 3.3.3; I'm pretty sure everything will work on previous gcc versions, but I don't know how far back we go. Also, just to check the easy part first, open a clean cygwin bash shell and do: make distclean && ./configure && make test If this doesn't work, can you send me the file src/libsrc/ncconfig.h? Something is going wrong in your configuration, but I don't know what! Ed -- Ed Hartnett -- address@hidden