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.
Jose, > To: address@hidden > From: Jose Quesada <address@hidden> > Subject: SORRY, FORGOT THE ATTACHMENTs: NetCDF on a debian Itanium 1 Machine > Organization: CU > Keywords: 200310030038.h930cjk1028498 The above message contained the following: > I have found some problems trying to install NetCDF on a debian Itanium 1 > Machine. ( I don't think there is a package or rpm for ia64 as yet). > > The configuration I'm using is: > export CC=/usr/bin/gcc > export CPPFLAGS=-Df2cFortran > export FC=/usr/bin/gcc > export FFLAGS=-Wno-globals > export CXX=/usr/bin/gcc > ./configure > > ... which is the one suggested in the install.html file for newer versions > of linux. > > The error that configure gets me is: > checking if Fortran "byte" is C "signed char"... configure: error: Could > not link conftestf.o and conftest.o > > The version of the compilers: > g77 --version > GNU Fortran 0.5.26 20000731 (Debian GNU/Linux IA64 experimental) > > gcc --version > 2.96 > > Here is the list of required info: > The standard output of the command "uname -a". > Linux muen210-86 2.4.19-ia64 #1 Mon Jan 27 12:53:56 MST 2003 ia64 unknown > > The contents of the file VERSION, which is in the top-level source > directory. > 3.5.1-beta13 > > The file "macros.make", which is created in the top-level source directory > by the configure script during step 6 above. > attached > > The absolute pathnames of all compilers (C, Fortran, C++) used in the > build process if they are not in the file "macros.make" > /usr/bin/gcc > /usr/bin/g77 > /usr/bin/g++ (same thing) > > (use the type(1) or which(1) utility to determine this). > The file "configure.log" from step 6 above. > attached > > Thanks a lot in advance, > -JOse > > -- > Jose Quesada, PhD. > > address@hidden Research associate > http://lsa.colorado.edu/~quesadaj Institute of Cognitive Science > University of Colorado (Boulder) > > Muenzinger psychology building Phone:303 492 1522 > office D447A Fax: 303 492 7177 > Campus Box 344 > University of Colorado at Boulder > Boulder, CO 80309-0344 > ------------CitNisqz2x37y2OouzColI > Content-Disposition: attachment; filename=configure.log > Content-Type: text/plain; name=configure.log > Content-Transfer-Encoding: 8bit > > configure: warning: Could not find working Fortran-90 compiler > configure: warning: The Fortran-90 interface will not be built > configure: error: Could not link conftestf.o and conftest.o > no > checking m4 flags... -B10000 > checking C compiler "/usr/bin/gcc"... works > checking how to make dependencies... false > checking for /usr/bin/g++... /usr/bin/g++ > checking C++ compiler "/usr/bin/g++"... works > checking how to run the C preprocessor... /usr/bin/gcc -E > checking user-defined Fortran-77 compiler "/usr/bin/gcc"... works > checking for Fortran .F compiler... > checking if Fortran-77 compiler handles *.F files... no > checking for Fortran preprocessor... /usr/bin/gcc -E > checking "/usr/bin/gcc" as Fortran-90 compiler... failed to build test program > checking for xlf90... no > checking for f90... no > checking for nm utility > checking for nm... nm > checking nm flags... > 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"... > ------------CitNisqz2x37y2OouzColI Just stops right there, eh? The reason for this should be in the file "config.log" (NB: not "configure.log"). Would you please send me that file. Regards, Steve Emmerson