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: Christian Bjerrum <address@hidden> >Subject: netCDF and HP-UX B.10.20 A 9000/730 >Organization: . >Keywords: 199711172212.PAA14501 Hi Christian, > Being very happy with using netCDF on a Cray, I now need it on a HP-UX > system. > As fare as I can tell Errors occure during the config testing. > Here is the info you need: > > HP-UX farallon B.10.20 A 9000/730 2009037665 two-user license > > 3.3.1 > VERSION (END) > > % which c89 > /usr/bin/c89 > > % which fort77 > /opt/fortran/bin/fort77 > > Output from configure script: > creating cache ./config.cache > checking for m4... m4 > checking user-defined C compiler "c89" > checking C compiler... works > checking how to make dependencies... false > checking for CC... no > checking for cxx... no > checking for c++... c++ > checking C++ compiler "c++"... works > checking how to run the C preprocessor... c89 -E > checking user-defined FORTRAN compiler "f77"... works > checking for FORTRAN .F compiler... > checking if FORTRAN 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 "integer*2" is C "short"... yes > checking if FORTRAN "integer*2" is C "int"... 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 > checking for math library > checking for -lc... no > checking for -lm... yes > checking for ar... ar > checking for ranlib... ranlib > checking for stdlib.h... yes > checking for sys/types.h... yes > checking for strerror... yes > checking for ftruncate... yes > checking for st_blksize in struct stat... no > checking whether cross-compiling... no > checking for IEEE floating point format... yes > checking for ANSI C header files... yes > checking for size_t... yes > checking for off_t... no > checking for ssize_t... no > checking for ptrdiff_t... yes > checking for uchar... no > checking whether char is unsigned... no > checking whether byte ordering is bigendian... yes > checking size of short... 2 > checking size of int... 4 > checking size of long... 4 > checking size of float... 4 > checking size of double... 8 > checking size of off_t... 4 > checking size of size_t... 4 > checking for manual-page index command... > checking binary distribution directory... > /home/ftp/pub/binary/dummy_system > updating cache ./config.cache > creating ./config.status > creating macros.make > udcreating fortran/nfconfig.inc > creating libsrc/ncconfig.h > > AND the config.log > > This file contains any messages produced by compilers while > running configure, to aid debugging if configure makes a mistake. > > configure:1017: c89 -c -D_HPUX_SCOURCE -DNDEBUG conftest.c 1>&5 Oops, I suspect the problem is that "-D_HPUX_SCOURCE" should be "-D_HPUX_SOURCE" instead (notice there is only one "C" in "SOURCE"). Try the following: 1. Go to the top-level netcdf-3 source directory. 2. Execute the command "make clean". 3. Remove the file "config.cache" if it exists. 4. Set the following environment variables to the indicated values: CPPFLAGS='-DNDEBUG -D_HPUX_SOURCE' CC=c89 CFLAGS=-O FC=fort77 FFLAGS='-O3 -w' The "_HPUX_SOURCE" should handle the "EEXIST" problem and the "-O3" should mollify the fort77(1) compiler. 5. Execute the configure script. Redirect standard output and standard error to a file. If an error occurs, then stop and send us the file. 6. Execute the command "make" Redirect standard output and standard error to a file. If an error occurs, then stop and send us the file. Note: f77 might work as well as fort77 for the Fortran-77 compiler, but we haven't tested that combination yet. > Making `all' in directory /us/users/cjb/netcdf-3.3.1/src/libsrc > > c89 -c -I. -D_HPUX_SCOURCE -DNDEBUG attr.c > c89 -c -I. -D_HPUX_SCOURCE -DNDEBUG dim.c > c89 -c -I. -D_HPUX_SCOURCE -DNDEBUG error.c > c89 -c -I. -D_HPUX_SCOURCE -DNDEBUG -DVERSION=`cat ../VERSION` > libvers > .c > c89 -c -I. -D_HPUX_SCOURCE -DNDEBUG nc.c > cc: "nc.c", line 834: error 1588: "EEXIST" undefined. > cc: "nc.c", line 834: error 1563: Expression in if must be scalar. > *** Error exit code 1 --Russ _____________________________________________________________________ Russ Rew UCAR Unidata Program address@hidden http://www.unidata.ucar.edu