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

20040804: SUSE 9.1 - configure script can not find compilers (cont.)

>From: "Leonard Montenegro" <address@hidden>
>Organization: ADEQ
>Keywords: 200407240202.i6O22Vex019235 netCDF configure Portland Group

Leonard,

>I keep getting errors when I initiate ./configure for netcdf 3.5.0
>I have copied the output below.
>Any idea why it keeps saying that the compilers fail during the test
>program?

A listing of the output from configure would typically not contain
enough information for us to figure out what is going on, but in
this case I think I can make an educated guess as to why you are
seeing failures:

There were known problems in netCDF 3.5.0 with newer GNU C++ compilers.
The solution is to use a more current relase of the netCDF, like
3.5.1.  You can FTP this release as follows:

machine: ftp.unidata.ucar.edu
user:    anonymous
pass:    address@hidden
directory: pub/netcdf
file:      netcdf-3.5.1.tar.Z

Please remove the 3.5.0 build attempt and try using 3.5.1.  Please
let us know if you continue to have problems.

Cheers,

Tom Yoksas

>user@linux:~/cmaq/netcdf-3.5.0/src> ./configure
>loading cache ./config.cache
>checking for top-level source-directory
>/home/user/cmaq/netcdf-3.5.0/src
>checking for m4 preprocessor
>checking for m4... no
>checking for gm4... no
>checking m4 flags... -B10000
>checking for xlc... (cached) cc
>checking C compiler "cc"... works
>checking how to make dependencies... false
>checking for CC... no
>checking for cxx... no
>checking for c++... c++
>checking C++ compiler "c++"... configure: warning: c++ failed on test
>program
>checking for g++... g++
>checking C++ compiler "g++"... configure: warning: g++ failed on test
>program
>checking for gcc... gcc
>checking C++ compiler "gcc"... configure: warning: gcc failed on test
>program
>configure: warning: Could not find working C++ compiler
>configure: warning: Setting CXX to the empty string
>configure: warning: The C++ interface will not be built
>checking how to run the C preprocessor... (cached) cc -E
>checking for f77... (cached) f77
>checking for Fortran .F compiler...
>checking if Fortran-77 compiler handles *.F files... yes
>checking "f77" as Fortran-90 compiler... failed to build test program
>checking for xlf90... no
>checking for f90... no
>configure: warning: Could not find working Fortran-90 compiler
>configure: warning: The Fortran-90 interface will not be built
>checking for nm utility
>checking for nm... (cached) 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"... yes
>checking if Fortran "byte" is C "short"... no
>checking if Fortran "byte" is C "int"... no
>checking if Fortran "byte" is C "long"... no
>checking if Fortran "integer*2" is C "short"... yes
>checking if Fortran "integer*2" is C "int"... no
>checking if Fortran "integer*2" is C "long"... 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 tanh in -lc... (cached) no
>checking for tanh in -lm... (cached) yes
>checking for ar utility
>checking for ar... (cached) ar
>checking ar flags... cru
>checking for nm utility
>checking for nm... (cached) nm
>checking nm flags...
>checking for ranlib... (cached) ranlib
>checking for stdlib.h... (cached) yes
>checking for sys/types.h... (cached) yes
>checking for strerror... (cached) yes
>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
>user@linux:~/cmaq/netcdf-3.5.0/src>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>>>> Unidata Support <address@hidden> 07/27/04 12:58 PM >>>
>>From: "Leonard Montenegro" <address@hidden>
>>Organization: ADEQ
>>Keywords: 200407240202.i6O22Vex019235 netCDF configure Portland Group
>
>Leonard,
>
>>>'configure' script is not setup to know where to look for them.  
>>
>>Can you please let me now how to set up the configure script to find
>the
>>PG compilers?
>
>The easiest thing for you to do is define the environment variables we
>talked about in previous emails.  Otherwise, each time you do a netCDF
>upgrade, you would be forced to muck with the contents of 'configure';
>this is a lot more work than defining the environment variables and
>could lead to a lot more problems.
>
>I suggest defining the environment variables in your shell-specific
>definition file: .cshrc for C Shell; .bashrc for bash; .profile for
>Bourne shell, etc.  By defining them in the shell definition file,
>you will not be forced into redefining them from the command line
>each time you want to build.
>
>>Or, can you tell me which compilers I should be using and where to put
>>them so the configure script can find them?
>
>For the platform you are working on, the best and easiest thing for
>you to do now is define the needed environment variables.
>
>>Thanks
>
>No worries.
>
>Cheers,
>
>Tom
>--
>****************************************************************************
><
>Unidata User Support                                    UCAR Unidata
>(303)497-8643                                                  P.O. Box
>address@hidden                                   Boulder, CO
>----------------------------------------------------------------------------
><
>Unidata WWW Service             
>----------------------------------------------------------------------------
><
>NOTE: All email exchanges with Unidata User Support are recorded in the
>Unidata inquiry tracking system and then made publically available
>through the web.  If you do not want to have your interactions made
>available in this way, you must let us know in each email you send to
>us.
>
--
NOTE: All email exchanges with Unidata User Support are recorded in the
Unidata inquiry tracking system and then made publically available
through the web.  If you do not want to have your interactions made
available in this way, you must let us know in each email you send to us.