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.
Andrew, [Your mail system is misconfigured. Your email address was "Andrew MacPherson <andrew@localhost.localdomain>" -- which is invalid. I've used your IP address. I strongly suggest that you contact your system administrator about this ASAP. --Steve] >Date: Wed, 14 Jun 2000 10:39:10 -0400 >From: Andrew MacPherson <andrew@localhost.localdomain> >Organization: ? >To: address@hidden >Subject: make failed >Keywords: 200006141439.e5EEdPT16857 In the above message, you wrote: > I'm not able to make the file libnet.cdf.a: > > A: Linux armpl4 2.2.14-5.0 #1 Tue Mar 7 21:07:39 EST 2000 i686 unknown > > B: 3.4 > > C: /usr/bin > > D: configure.log file*** > > loading cache ./config.cache > checking for m4... (cached) m4 > checking for xlc... (cached) cc > checking C compiler... works > checking how to make dependencies... false > checking for CC... (cached) c++ > checking C++ compiler "c++"... works > checking how to run the C preprocessor... (cached) cc -E > checking for f77... (cached) f77 > FORTRAN 77 Compiler 4.6, Copyright (c) 1987-1999, Absoft Corp. > checking for Fortran .F compiler... > checking if Fortran compiler handles *.F files... FORTRAN 77 Compiler 4.6, > Copyright (c) 1987-1999, Absoft Corp. > yes > checking for C-equivalent to Fortran routine "SUB"... FORTRAN 77 Compiler > 4.6, Copyright (c) 1987-1999, Absoft Corp. > sub > checking for Fortran "byte"... FORTRAN 77 Compiler 4.6, Copyright (c) > 1987-1999, Absoft Corp. > yes > checking for Fortran "integer*2"... FORTRAN 77 Compiler 4.6, Copyright (c) > 1987-1999, Absoft Corp. > yes > checking if Fortran "byte" is C "signed char"... FORTRAN 77 Compiler 4.6, > Copyright (c) 1987-1999, Absoft Corp. > yes > checking if Fortran "byte" is C "short"... FORTRAN 77 Compiler 4.6, Copyright > (c) 1987-1999, Absoft Corp. > no > checking if Fortran "byte" is C "int"... FORTRAN 77 Compiler 4.6, Copyright > (c) 1987-1999, Absoft Corp. > no > checking if Fortran "byte" is C "long"... FORTRAN 77 Compiler 4.6, Copyright > (c) 1987-1999, Absoft Corp. > no > checking if Fortran "integer*2" is C "short"... FORTRAN 77 Compiler 4.6, > Copyright (c) 1987-1999, Absoft Corp. > yes > checking if Fortran "integer*2" is C "int"... FORTRAN 77 Compiler 4.6, > Copyright (c) 1987-1999, Absoft Corp. > no > checking if Fortran "integer*2" is C "long"... FORTRAN 77 Compiler 4.6, > Copyright (c) 1987-1999, Absoft Corp. > no > checking if Fortran "integer" is C "int"... FORTRAN 77 Compiler 4.6, > Copyright (c) 1987-1999, Absoft Corp. > yes > checking if Fortran "real" is C "float"... FORTRAN 77 Compiler 4.6, Copyright > (c) 1987-1999, Absoft Corp. > yes > checking if Fortran "doubleprecision" is C "double"... FORTRAN 77 Compiler > 4.6, Copyright (c) 1987-1999, Absoft Corp. > yes > checking for Fortran-equivalent to netCDF "byte"... FORTRAN 77 Compiler 4.6, > Copyright (c) 1987-1999, Absoft Corp. > byte > checking for Fortran-equivalent to netCDF "short"... FORTRAN 77 Compiler 4.6, > Copyright (c) 1987-1999, Absoft Corp. > integer*2 > checking for math library > checking for -lc... (cached) no > checking for -lm... (cached) yes > checking for ar... (cached) ar > checking for ranlib... (cached) ranlib > checking for stdlib.h... (cached) yes > checking for sys/types.h... (cached) yes > checking for strerror... (cached) yes > checking whether cross-compiling... (cached) no > checking for working ftruncate()... yes > checking for working alloca.h... (cached) yes > checking for alloca... (cached) yes > checking for st_blksize in struct stat... (cached) yes > checking for IEEE floating point format... yes > checking for ANSI C header files... (cached) yes > checking for size_t... (cached) yes > checking for off_t... (cached) yes > checking for ssize_t... (cached) yes > checking for ptrdiff_t... (cached) yes > checking for uchar... (cached) no > checking whether char is unsigned... (cached) no > checking whether byte ordering is bigendian... (cached) no > checking size of short... (cached) 2 > checking size of int... (cached) 4 > checking size of long... (cached) 4 > checking size of float... (cached) 4 > checking size of double... (cached) 8 > checking size of off_t... (cached) 4 > checking size of size_t... (cached) 4 > checking for manual-page index command... > checking binary distribution directory... /home/ftp/pub/binary/dummy_system > creating ./config.status > creating macros.make > udcreating fortran/nfconfig.inc > fortran/nfconfig.inc is unchanged > creating libsrc/ncconfig.h > libsrc/ncconfig.h is unchanged > > > *** config.log file *** > > This file contains any messages produced by compilers while > running configure, to aid debugging if configure makes a mistake. > > configure:1020: cc -c -O -DNDEBUG conftest.c 1>&5 > configure:1153: c++ -c -DNDEBUG conftest.C 1>&5 configure:1373: f77 -c -O conftest.f > configure:1422: f77 -o conftest -O conftest.F > warning on line 4 of conftest.F: local variable r never referenced > configure:1463: f77 -c -O conftest.f > configure:1498: f77 -c -O conftest.f > configure:1521: f77 -c -O conftest.f > configure:1555: cc -c -DNDEBUG -O conftest.c > configure:1557: f77 -O -c conftestf.f > configure:1559: f77 -o conftest -O conftestf.o conftest.o > configure:1561: ./conftest > configure:1602: cc -c -DNDEBUG -O conftest.c > configure:1604: f77 -O -c conftestf.f > configure:1606: f77 -o conftest -O conftestf.o conftest.o > configure:1608: ./conftest > configure:1649: cc -c -DNDEBUG -O conftest.c > configure:1651: f77 -O -c conftestf.f > configure:1653: f77 -o conftest -O conftestf.o conftest.o > configure:1655: ./conftest > configure:1696: cc -c -DNDEBUG -O conftest.c > configure:1698: f77 -O -c conftestf.f > configure:1700: f77 -o conftest -O conftestf.o conftest.o > configure:1702: ./conftest > configure:1747: cc -c -DNDEBUG -O conftest.c > configure:1749: f77 -O -c conftestf.f > configure:1751: f77 -o conftest -O conftestf.o conftest.o > configure:1753: ./conftest > configure:1794: cc -c -DNDEBUG -O conftest.c > configure:1796: f77 -O -c conftestf.f > configure:1798: f77 -o conftest -O conftestf.o conftest.o > configure:1800: ./conftest > configure:1841: cc -c -DNDEBUG -O conftest.c > configure:1843: f77 -O -c conftestf.f > configure:1845: f77 -o conftest -O conftestf.o conftest.o > configure:1847: ./conftest > configure:1890: cc -c -DNDEBUG -O conftest.c > configure:1892: f77 -O -c conftestf.f > configure:1894: f77 -o conftest -O conftestf.o conftest.o > configure:1896: ./conftest > configure:1937: cc -c -DNDEBUG -O conftest.c > configure:1939: f77 -O -c conftestf.f > configure:1941: f77 -o conftest -O conftestf.o conftest.o > configure:1943: ./conftest > configure:1984: cc -c -DNDEBUG -O conftest.c > configure:1986: f77 -O -c conftestf.f > configure:1988: f77 -o conftest -O conftestf.o conftest.o > configure:1990: ./conftest > configure:2023: f77 -c -O conftest.f > warning on line 2 of conftest.f: local variable foo never referenced > configure:2044: f77 -c -O conftest.f > warning on line 2 of conftest.f: local variable foo never referenced > configure:2398: cc -o conftest -O -DNDEBUG conftest.c 1>&5 > configure:2702: cc -o conftest -O -DNDEBUG conftest.c 1>&5 > > > *** make.log file *** > > make[1]: Entering directory `/home/andrew/netCDF/netcdf-3.4/src' > > Making `all' in directory /home/andrew/netCDF/netcdf-3.4/src/libsrc > > make[2]: Entering directory `/home/andrew/netCDF/netcdf-3.4/src/libsrc' > cc -c -O -I. -DNDEBUG attr.c > cc -c -O -I. -DNDEBUG dim.c > cc -c -O -I. -DNDEBUG error.c > make[2]: Leaving directory `/home/andrew/netCDF/netcdf-3.4/src/libsrc' > make[1]: Leaving directory `/home/andrew/netCDF/netcdf-3.4/src' Without an error message from the last command above, it's difficult to diagnose the problem. Would you please try dropping into the "libsrc/" subdirectory and manually executing the command cc -c -O -I. -DNDEBUG error.c Send me any error messages that result. Regards, Steve Emmerson <http://www.unidata.ucar.edu>