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

[netCDF #BYG-802466]: Cofiguring and building netCDF on Red HAt Linux

> I was trying to load on my RadHAt Linux machine that has C and C++ compilers
but the following is displayed
>
>
>
> [root@dawit]# ./configure --disable-f90
>
> configure: netCDF 4.0
>
> checking build system type... x86_64-unknown-linux-gnu
>
> checking host system type... x86_64-unknown-linux-gnu
>
> checking for a BSD-compatible install... /usr/bin/install -c
>
> checking whether build environment is sane... yes
>
> checking for a thread-safe mkdir -p... /bin/mkdir -p
>
> checking for gawk... gawk
>
> checking whether make sets $(MAKE)... yes
>
> configure: checking user options
>
> checking whether CXX is set to ''... no
>
> checking whether FC is set to ''... no
>
> checking whether F90 is set to ''... no
>
> checking whether this is a netCDF-4.x build... yes
>
> configure: Processing NetCDF-4 options.
>
> checking whether netCDF-4 is to be built...
>
> checking whether DAP client is to be built...
>
> checking whether new netCDF-4 C++ API is to be built... no
>
> checking whether HDF5 should do data conversions...
>
> checking whether extra example tests should be run...
>
> checking whether parallel IO tests should be run... no
>
> checking whether a location for the HDF5 library was specified... .
>
> checking whether a location for the ZLIB library was specified...
>
> checking whether a location for the SZLIB library was specified...
>
> checking whether netCDF-4 logging is enabled...
>
> checking whether netCDF extra tests should be run (developers only)... no
>
> checking whether documentation is to be installed... no
>
> checking whether Fortran compiler(s) should be tested during configure... yes
>
> checking whether configure should try to set compiler flags... yes
>
> checking whether FFIO will be used... no
>
> checking whether to skip C++, F77, or F90 APIs if compiler is broken... yes
>
> checking whether only the C library is desired... no
>
> checking whether examples should be built... yes
>
> checking whether F77 API is desired... yes
>
> checking whether F90 API is desired... no
>
> checking whether fortran type sizes should be checked... yes
>
> checking whether C API is desired... yes
>
> checking where to get netCDF C-only library for separate fortran
libraries...
>
> checking whether CXX API is desired... yes
>
> checking whether v2 netCDF API should be built... yes
>
> checking whether the ncgen/ncdump should be built... yes
>
> checking whether large file (> 2GB) tests should be run... no
>
> checking whether benchmaks should be run (experimental)... no
>
> checking whether extreme numbers should be used in tests... yes
>
> checking where to put large temp files if large file tests are run... .
>
> checking whether a win32 DLL is desired... no
>
> checking whether separate fortran libs are desired... no
>
> configure: finding C compiler
>
> checking for xlc... no
>
> checking for cc... cc
>
> 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 cc accepts -g... yes
>
> checking for cc option to accept ISO C89... none needed
>
> checking for style of include used by make... GNU
>
> checking dependency style of cc... gcc3
>
> checking whether cc understands -c and -o together... yes
>
> checking for an ANSI C-conforming const... yes
>
> configure: finding Fortran compiler (will not be used if Fortran API is not
desired)
>
> checking for xlf90... no
>
> checking for fort... no
>
> checking for xlf95... no
>
> checking for ifort... no
>
> checking for ifc... no
>
> checking for efc... no
>
> checking for pgf95... pgf95
>
> checking whether we are using the GNU Fortran compiler... no
>
> checking whether pgf95 accepts -g... no
>
> checking for xlf... no
>
> checking for fort... no
>
> checking for xlf95... no
>
> checking for ifort... no
>
> checking for ifc... no
>
> checking for efc... no
>
> checking for pgf77... pgf77
>
> checking whether we are using the GNU Fortran 77 compiler... no
>
> checking whether pgf77 accepts -g... no
>
> configure: finding C++ compiler (will not be used if C++ API is not desired)
>
> checking for cl... no
>
> checking for KCC... no
>
> checking for CC... no
>
> checking for cxx... no
>
> checking for cc++... no
>
> checking for xlC... no
>
> checking for aCC... no
>
> checking for c++... c++
>
> checking whether we are using the GNU C++ compiler... yes
>
> checking whether c++ accepts -g... yes
>
> checking dependency style of c++... gcc3
>
> configure: setting up libtool
>
> checking for a sed that does not truncate output... /bin/sed
>
> checking for grep that handles long lines and -e... /bin/grep
>
> checking for egrep... /bin/grep -E
>
> checking for fgrep... /bin/grep -F
>
> checking for ld used by cc... /usr/bin/ld
>
> checking if the linker (/usr/bin/ld) is GNU ld... yes
>
> checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
>
> checking the name lister (/usr/bin/nm -B) interface... BSD nm
>
> checking whether ln -s works... yes
>
> checking the maximum length of command line arguments... 98304
>
> checking whether the shell understands some XSI constructs... yes
>
> checking whether the shell understands "+="... no
>
> checking for /usr/bin/ld option to reload object files... -r
>
> checking how to recognize dependent libraries... pass_all
>
> checking for ar... ar
>
> checking for strip... strip
>
> checking for ranlib... ranlib
>
> checking command to parse /usr/bin/nm -B output from cc object... ok
>
> checking how to run the C preprocessor... cc -E
>
> checking for ANSI C header files... yes
>
> checking for sys/types.h... yes
>
> checking for sys/stat.h... yes
>
> checking for stdlib.h... yes
>
> checking for string.h... yes
>
> checking for memory.h... yes
>
> checking for strings.h... yes
>
> checking for inttypes.h... yes
>
> checking for stdint.h... yes
>
> checking for unistd.h... yes
>
> checking for dlfcn.h... yes
>
> checking whether we are using the GNU C++ compiler... (cached) yes
>
> checking whether c++ accepts -g... (cached) yes
>
> checking dependency style of c++... (cached) gcc3
>
> checking how to run the C++ preprocessor... c++ -E
>
> checking whether we are using the GNU Fortran 77 compiler... (cached) no
>
> checking whether pgf77 accepts -g... (cached) no
>
> checking whether we are using the GNU Fortran compiler... (cached) no
>
> checking whether pgf77 accepts -g... (cached) no
>
> checking for objdir... .libs
>
> checking if cc supports -fno-rtti -fno-exceptions... no
>
> checking for cc option to produce PIC... -fPIC -DPIC
>
> checking if cc PIC flag -fPIC -DPIC works... yes
>
> checking if cc static flag -static works... yes
>
> checking if cc supports -c -o file.o... yes
>
> checking if cc supports -c -o file.o... (cached) yes
>
> checking whether the cc linker (/usr/bin/ld -m elf_x86_64) supports shared
libraries... yes
>
> checking dynamic linker characteristics... GNU/Linux ld.so
>
> checking how to hardcode library paths into programs... immediate
>
> checking whether stripping libraries is possible... yes
>
> checking if libtool supports shared libraries... yes
>
> checking whether to build shared libraries... no
>
> checking whether to build static libraries... yes
>
> checking for ld used by c++... /usr/bin/ld -m elf_x86_64
>
> checking if the linker (/usr/bin/ld -m elf_x86_64) is GNU ld... yes
>
> checking whether the c++ linker (/usr/bin/ld -m elf_x86_64) supports shared
libraries... yes
>
> checking for c++ option to produce PIC... -fPIC -DPIC
>
> checking if c++ PIC flag -fPIC -DPIC works... yes
>
> checking if c++ static flag -static works... yes
>
> checking if c++ supports -c -o file.o... yes
>
> checking if c++ supports -c -o file.o... (cached) yes
>
> checking whether the c++ linker (/usr/bin/ld -m elf_x86_64) supports shared
libraries... yes
>
> checking dynamic linker characteristics... GNU/Linux ld.so
>
> checking how to hardcode library paths into programs... immediate
>
> checking if libtool supports shared libraries... yes
>
> checking whether to build shared libraries... no
>
> checking whether to build static libraries... yes
>
> checking for pgf77 option to produce PIC... -fpic
>
> checking if pgf77 PIC flag -fpic works... no
>
> checking if pgf77 static flag -Bstatic works... no
>
> checking if pgf77 supports -c -o file.o... no
>
> checking if pgf77 supports -c -o file.o... (cached) no
>
> checking whether the pgf77 linker (/usr/bin/ld -m elf_x86_64) supports shared
libraries... yes
>
> checking dynamic linker characteristics... GNU/Linux ld.so
>
> checking how to hardcode library paths into programs... immediate
>
> checking if libtool supports shared libraries... yes
>
> checking whether to build shared libraries... no
>
> checking whether to build static libraries... yes
>
> libtool.m4: error: problem compiling FC test program
>
> checking for pgf77 option to produce PIC... -fpic
>
> checking if pgf77 PIC flag -fpic works... no
>
> checking if pgf77 static flag -Bstatic works... no
>
> checking if pgf77 supports -c -o file.o... no
>
> checking if pgf77 supports -c -o file.o... (cached) no
>
> checking whether the pgf77 linker (/usr/bin/ld -m elf_x86_64) supports shared
libraries... yes
>
> checking dynamic linker characteristics... GNU/Linux ld.so
>
> checking how to hardcode library paths into programs... immediate
>
> configure: finding other utilities
>
> checking for a BSD-compatible install... /usr/bin/install -c
>
> configure: trying to set fortran flags for this platform
>
> configure: trying to set flags for this platform
>
> checking if _HPUX_SOURCE should be set... no
>
> checking if Solaris -Xa option is needed... CFLAGS=-g -O2
>
> checking if we need to set _LARGE_FILES despite results of previous tests...
_LARGE_FILES=
>
> checking for special C compiler options needed for large files... no
>
> checking for _FILE_OFFSET_BITS value needed for large files... no
>
> configure: displaying some results
>
> checking CPPFLAGS...
>
> checking CC CFLAGS... cc -g -O2
>
> checking type cc... cc is /usr/bin/cc
>
> checking CXX... c++
>
> checking CXXFLAGS... -g -O2
>
> checking type c++... c++ is /usr/bin/c++
>
> checking FC... pgf77
>
> checking FFLAGS...
>
> checking type pgf77... pgf77 is /usr/local/pgi/linux86-64/7.0/bin/pgf77
>
> checking F90... unset
>
> checking AR... ar
>
> checking AR_FLAGS... cru
>
> checking type ar... ar is /usr/bin/ar
>
> checking NM... /usr/bin/nm -B
>
> checking NMFLAGS...
>
> checking for /usr/bin/nm... /usr/bin/nm -B
>
> checking nm flags...
>
> checking for C-equivalent to Fortran routine "SUB"... configure: error: Could
not compile conftest.f
>
>
>
> ----------------------
>
>
>
> What should I correct to get it running properly?
>
> Thanks,
>
> Feyera
>
>

Howdy Feyera!

Something is wrong with your fortran compiler. Look towards the end of the
config.log file to find out what is wrong.

Basically, the configure script compiles some simple fortran programs. If that
fails, it gives up. If you don't want the fortran APIs you can run configure
with --disable-f77 and they won't be built. If you want to specify another
fortran compiler, set the environmental variable FC before running configure.

Please let me know if you need more help.

Thanks,

Ed

Ticket Details
===================
Ticket ID: BYG-802466
Department: Support netCDF
Priority: Normal
Status: Closed