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.
Dear Elke, >Date: Fri, 24 Oct 1997 8:58:43 MET >From: "E.Hocke" <address@hidden> >Organization: ? >To: address@hidden (Steve Emmerson) >Subject: Re: 971023: building under HP-UX A.09.05 using /usr/softbench /bin/c89 >Keywords: 199710231414.IAA16117 In the above message, you wrote: > Dear Steve, > as you see with this mail, there are still the same?? > problems while compiling the package. (same output as before) > The environmental variable -DhpuxFortran added to CPPFLAGS > could not solve the problem. > So I would like to send you now both - the configuration > output and the output of the comand make. > ----------------------------------------------------------- > > configuration output > > ----------------------------------------------------------- > > creating cache ./config.cache > checking for m4... m4 > checking user-defined C compiler "/usr/softbench/bin/c89" > checking C compiler... works > checking how to make dependencies... false > checking for /usr/softbench/bin/cc... /usr/softbench/bin/cc > checking C++ compiler "/usr/softbench/bin/cc"... works > checking how to run the C preprocessor... /usr/softbench/bin/c89 -E > checking user-defined FORTRAN compiler "/usr/softbench/bin/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... yes > 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... yes > checking for ssize_t... yes > 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 > > ----------------------------------------------------------- > > make output > > ----------------------------------------------------------- > > Making `all' in directory /users/kd005/NCEP-CD/netcdf-3.3.1/src/libsrc > > /usr/softbench/bin/c89 -c -O -I. -DNDEBUG -DhpuxFortran dim.c > /usr/softbench/bin/c89 -c -O -I. -DNDEBUG -DhpuxFortran error.c > /usr/softbench/bin/c89 -c -O -I. -DNDEBUG -DhpuxFortran -DVERSION=`cat > ../VERSION` libvers.c > /usr/softbench/bin/c89 -c -O -I. -DNDEBUG -DhpuxFortran nc.c > /usr/softbench/bin/c89 -c -O -I. -DNDEBUG -DhpuxFortran ncio.c > /usr/softbench/bin/c89 -c -O -I. -DNDEBUG -DhpuxFortran ncx.c > /usr/softbench/bin/c89 -c -O -I. -DNDEBUG -DhpuxFortran putget.c > /usr/softbench/bin/c89 -c -O -I. -DNDEBUG -DhpuxFortran string.c > /usr/softbench/bin/c89 -c -O -I. -DNDEBUG -DhpuxFortran v1hpg.c > /usr/softbench/bin/c89 -c -O -I. -DNDEBUG -DhpuxFortran v2i.c > /usr/softbench/bin/c89 -c -O -I. -DNDEBUG -DhpuxFortran var.c > ar cru libnetcdf.a attr.o dim.o error.o libvers.o nc.o ncio.o > ncx.o putget.o string.o v1hpg.o v2i.o var.o > ranlib libnetcdf.a > > Returning to directory /users/kd005/NCEP-CD/netcdf-3.3.1/src > > > Making `all' in directory /users/kd005/NCEP-CD/netcdf-3.3.1/src/fortran > > /usr/softbench/bin/c89 -c -O -I../libsrc -DNDEBUG -DhpuxFortran > fort-attio.c > *** Error code 1 > *** Error code 1 > *** Error code 1 The above doesn't provide much diagnostic information. What do you get when you manually execute the above compilation command in the fortran/ subdirectory? > > Thank you very much for your help > Yours sincerely, > Elke Hocke > > <address@hidden> -------- Steve Emmerson <http://www.unidata.ucar.edu>