[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: 20050805:Netcdf configure error

Unidata Support <address@hidden> writes:

> ------- Forwarded Message
>
>>To: address@hidden
>>From: "Waylon.Collins" <address@hidden>
>>Subject: Netcdf configure error
>>Organization: UCAR/Unidata
>>Keywords: 200508051510.j75FAAjo019995
>
> This is a multi-part message in MIME format.
>
> --Boundary_(ID_IB7SrkrCuXZmuzjTm1T4fw)
> Content-type: text/plain; charset=ISO-8859-1; format=flowed
> Content-transfer-encoding: 7BIT
>
> Dear Sir/Madam:
>
> I am trying to install netcdf-3.6.1_beta3. However, the attached message 
> reveals the output to an unsuccessful "./configure" run. (The same 
> output also occurred for netcdf-3.6.0-p1.) I added the the last line of 
> this output, which contains information about my computer via the 
> "uname" command. Any idea what the problem could be? Further, what are 
> possible solutions to the problem?
>
> ./configure
> checking build system type... x86_64-unknown-linux-gnu
> checking host system type... x86_64-unknown-linux-gnu
> configure: WARNING: FFLAGS=-O -mp
> checking Where to put large files... .
> checking for top-level source-directory... /usr/local/netcdf-3.6.1-beta3/src
> checking for C compiler default output file name... a.out
> checking whether the C compiler works... yes
> checking whether we are cross compiling... no
> checking for suffix of executables...
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... yes
> checking whether /usr/bin/gcc accepts -g... yes
> checking for /usr/bin/gcc option to accept ANSI C... none needed
> checking whether we are using the GNU C++ compiler... yes
> checking whether /usr/bin/g++ accepts -g... yes
> checking C++ compiler "/usr/bin/g++"... works
> configure: WARNING: linux-gnu FC=linux-gnu ifort
> checking if we need special ifort options on Linux... configure: WARNING: 
> "linux ifort F90FLAGS="
> configure: WARNING: "not mp"
> F90FLAGS= -mp
> checking if we need special f90 options on AIX with xlf90... F90LAGS=
> checking whether we are using the GNU Fortran compiler... no
> checking whether ifort accepts -g... yes
> configure: WARNING: FC=ifort CPPFLAGS=-DNDEBUG -DpgiFortran
> checking if Fortran-related pre-processor flag needed... -DNDEBUG -DpgiFortran
> checking user-defined Fortran-90 compiler "ifort"... works
> configure: checking for m4 preprocessor...
> checking for m4... m4
> checking m4 flags... -B10000
> checking how to make dependencies... false
> checking if we need to set _LARGE_FILES despite results of previous tests...
> checking for special C compiler options needed for large files... no
> checking for _FILE_OFFSET_BITS value needed for large files... no
> checking for _LARGE_FILES value needed for large files... no
> configure: checking for ar utility...
> checking for ar... ar
> checking ar flags... cru
> configure: checking for nm utility...
> checking for nm... nm
> checking nm flags...
> checking for ranlib... ranlib
> checking for a BSD-compatible install... /usr/bin/install -c
> checking CPPFLAGS... -DNDEBUG -DpgiFortran
> checking CC CFLAGS... /usr/bin/gcc -g
> checking type /usr/bin/gcc... /usr/bin/gcc is /usr/bin/gcc
> checking CXX... /usr/bin/g++
> checking CXXFLAGS... -g -O2
> checking type /usr/bin/g++... /usr/bin/g++ is /usr/bin/g++
> checking FC... ifort
> checking FFLAGS... -O -mp
> checking type ifort... ifort is /opt/intel_fc/bin/ifort
> checking F90... ifort
> checking F90FLAGS...  -mp
> checking type ifort... ifort is /opt/intel_fc/bin/ifort
> checking AR... ar
> checking ARFLAGS... cru
> checking type ar... ar is /usr/bin/ar
> checking NM... nm
> checking NMFLAGS...
> checking type nm... nm is /usr/bin/nm
> checking for SunOS Fortran -ftrap= option...
> checking how to run the C preprocessor... /usr/bin/gcc -E
> checking user-defined Fortran-77 compiler "ifort"... works
> checking for Fortran .F compiler...
> checking if Fortran-77 compiler handles *.F files... no
> checking for Fortran preprocessor... /usr/bin/gcc -E
> 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"... configure: error: Could not 
> link conftestf.o and conftest.o
>
> 2.4.21-32.0.1.EL #1 SMP Tue May 17 17:52:26 EDT 2005 x86_64 x86_64 x86_64 
> GNU/Linux
>
>

Looks like configure can't get your fortran compiler to work. Look
towards the end of config.log to see why. 

If netCDF's configure can't get your fortran compiler to work, it
gives up, because it assumes you want the fortran API. If you don't
want the API, set environmental variable FC to '' (that is, empty, or
null). Then rerun configure.

If you do want the fortran API, then do you want to use the Intel
fortran compiler that the configure is finding? (ifort). This compiler
requires you to have certain environment variables set correctly
before it works. Do you have ifort set up? Can you compile a trivially
simple fortran program from the command line with ifort?

Thanks,

Ed

-- 
Ed Hartnett  -- address@hidden