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.
Bill, >Date: Tue, 15 Jul 1997 14:53:15 -0400 >From: Bill Hudson <address@hidden> >Organization: Pennsylvania State University/Applied Research Laboratory >To: Steve Emmerson <address@hidden> >Subject: Re: 970617: building netCDF on an HP-UX <something> >Keywords: 199707151311.HAA19835 In the above message, you wrote: > I did as you instructed. I don't have a fortran compiler. The HP 9000/700 > is running "HP-UX 8.07". During "./configure" I received a warning, could > not detect a fortran compiler. You may safely ignore the warning from the configure script about the lack of a Fortran compiler. > and the following information in a file: > ------------- > creating cache ./config.cache > checking for m4... m4 > checking for xlc... no > checking for c89... no > checking for acc... no > checking for cc... cc > checking C compiler... works > checking for how to make dependencies... false > checking for CC... CC > checking C++ compiler "CC"... works > checking for fort77... no > checking for math library > checking for -lc... no > checking for -lm... yes > checking for ar... ar > checking for ranlib... ranlib > checking how to run the C preprocessor... /lib/cpp > checking for stdlib.h... no > checking for sys/types.h... no > 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... no > checking for ANSI C header files... no > checking for size_t... yes > checking for off_t... yes > checking for ssize_t... yes > checking for ptrdiff_t... no > 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 command to create manual-page index... > checking binary distribution directory... /home/ftp/pub/binary/dummy_system > updating cache ./config.cache > creating ./config.status > creating macros.make > creating libsrc/ncconfig.h > libsrc/ncconfig.h is unchanged > creating fortran/netcdf-cpp.inc > fortran/netcdf-cpp.inc is unchanged > --------------------- The above looks good. > > The C compiler is whatever HP had in the HP-UX 8.07 that was installed in > the computer. The results of the make output into a file were somewhat > similiar to what I sent before. > > ---------------------- > > Making `all' in directory /exthd/ftp/pub/gmt/netcdf-3.3/src/libsrc > > cc -c -O -I. -DNDEBUG attr.c > cc: "/usr/include/stddef.h", line 26: error 1642: Duplicate type specifier > "int" > : ignored. > cc: "netcdf.h", line 178: warning 5: "const" will become a keyword. > cc: "netcdf.h", line 178: error 1000: Unexpected symbol: "char". > cc: "netcdf.h", line 181: warning 5: "const" will become a keyword. > cc: "netcdf.h", line 179: error 1705: Function prototypes are an ANSI feature. > cc: "netcdf.h", line 181: error 1000: Unexpected symbol: "char". > cc: "netcdf.h", line 182: error 1705: Function prototypes are an ANSI feature. > cc: "netcdf.h", line 185: warning 5: "const" will become a keyword. > cc: "netcdf.h", line 185: error 1000: Unexpected symbol: "char". > cc: error 2017: Cannot recover from earlier errors, terminating. > cc: warning 422: Unknown option "O" ignored. > *** Error code 1 > *** Error code 1 > *** Error code 1 > ------------------------- > Anything you can let me know is appreciated. You're in trouble. The netCDF distribution can *only* be built by a Standard C compiler and your "cc" compiler isn't standard. Check your manual page on the "cc" compiler. Is there a flag to make it a Standard C compiler? Is the GNU C compiler (gcc) installed? -------- Steve Emmerson <http://www.unidata.ucar.edu>