Hi Keerthi, Please send us the config.log that resulted from running configure. Thanks. --Russ > I am installing netcdf-4 and have been getting the following error. > > I have tried looking into config.log file. However, i could not understand > what and how to corrct. please consider this request and suggest me > methods to correct this error. > > > configure: finding Fortran compiler (will not be used if Fortran API is not > desired) > checking for gfortran... no > checking for g95... no > checking for xlf95... no > checking for f95... no > checking for fort... no > checking for ifort... no > checking for ifc... no > checking for efc... no > checking for pgfortran... no > checking for pgf95... no > checking for lf95... no > checking for ftn... no > checking for xlf90... no > checking for f90... no > checking for pgf90... no > checking for pghpf... no > checking for epcf90... no > checking for g77... no > checking for xlf... no > checking for f77... f77 > checking whether we are using the GNU Fortran compiler... yes > checking whether f77 accepts -g... yes > checking for f77... f77 > checking whether we are using the GNU Fortran 77 compiler... yes > checking whether f77 accepts -g... yes > configure: setting up Fortran 90 > checking what FC is set to... f77 > checking for Fortran flag to compile .f90 files... unknown > configure: error: Fortran could not compile .f90 files > address@hidden:~/mhm/netcdf-4.1.3$ cd .. > address@hidden:~/mhm$ CPPFLAGS=-I/home/username/local/include > LDFLAGS=-L/home/iitgn/local/lib ./configure --prefix=/home/iitgn/loca > configure: netCDF 4.1.2 > checking build system type... x86_64-unknown-linux-gnu > checking host system type... x86_64-unknown-linux-gnu > checking target 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... no > checking for mawk... mawk > 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 a NCIO_MINBLOCKSIZE was specified... 256 > checking whether udunits is to be built... no > checking if fsync support is enabled... yes > checking whether extra valgrind tests should be run... no > checking whether libcf is to be built... no > checking whether a location for the HDF4 library was specified... > checking whether reading of HDF4 SD files is to be enabled... no > checking whether to fetch some sample HDF4 files from Unidata ftp site to > test HDF4 reading (requires wget)... no > checking whether parallel I/O for classic and 64-bit offset files using > parallel-netcdf is to be enabled... no > checking whether a location for the parallel-netcdf library was > specified... no > checking whether new netCDF-4 C++ API is to be built... no > checking whether extra example tests should be run... no > 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 a default chunk size in bytes was specified... 4194304 > checking whether a maximum per-variable cache size for HDF5 was > specified... 67108864 > checking whether a number of chunks for the default per-variable cache was > specified... 10 > checking whether a default file cache size for HDF5 was specified... 4194304 > checking whether a default file cache maximum number of elements for HDF5 > was specified... 1009 > checking whether a default cache preemption for HDF5 was specified... 0.75 > checking whether netCDF-4 logging is enabled... no > checking whether cdmremote client is to be built... no > checking whether DAP client is to be built... yes > checking whether a path for curl-config was specified... no > checking whether a location for curl installation was specified... no > checking checking whether a location for curl-config found... no > configure: error: Cannot locate neither curl-config or a curl directory > address@hidden:~/mhm$ cd netcdf-4.1.3/ > address@hidden:~/mhm/netcdf-4.1.3$ > CPPFLAGS=-I/home/username/local/include LDFLAGS=-L/home/iitgn/local/lib > ./configure --prefix=/home/iitgn/loca > configure: netCDF 4.1.3 > checking build system type... x86_64-unknown-linux-gnu > checking host system type... x86_64-unknown-linux-gnu > checking target 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... no > checking for mawk... mawk > 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 a NCIO_MINBLOCKSIZE was specified... 256 > checking whether udunits is to be built... no > checking if fsync support is enabled... yes > checking whether extra valgrind tests should be run... no > checking whether we should try to build netCDF-4... yes > checking whether libcf is to be built... no > checking whether reading of HDF4 SD files is to be enabled... no > checking whether to fetch some sample HDF4 files from Unidata ftp site to > test HDF4 reading (requires wget)... no > checking whether parallel I/O for classic and 64-bit offset files using > parallel-netcdf is to be enabled... no > checking whether new netCDF-4 C++ API is to be built... no > checking whether extra example tests should be run... no > checking whether parallel IO tests should be run... no > checking whether a default chunk size in bytes was specified... 4194304 > checking whether a maximum per-variable cache size for HDF5 was > specified... 67108864 > checking whether a number of chunks for the default per-variable cache was > specified... 10 > checking whether a default file cache size for HDF5 was specified... 4194304 > checking whether a default file cache maximum number of elements for HDF5 > was specified... 1009 > checking whether a default cache preemption for HDF5 was specified... 0.75 > checking whether netCDF-4 logging is enabled... no > checking whether cdmremote client is to be built... no > checking whether DAP client is to be built... yes > checking for style of include used by make... GNU > checking for gcc... gcc > checking whether the C compiler works... yes > checking for C compiler default output file name... a.out > checking for suffix of executables... > checking whether we are cross compiling... no > checking for suffix of object files... o > checking whether we are using the GNU C compiler... yes > checking whether gcc accepts -g... yes > checking for gcc option to accept ISO C89... none needed > checking dependency style of gcc... gcc3 > checking for curl_easy_setopt in -lcurl... no > configure: libcurl not found; disabling dap and cdmremote support > checking whether dap remote testing should be enabled (default on)... no > checking whether the time-consuming dap tests should be enabled (default > off)... no > checking whether netCDF extra tests should be run (developers only)... no > checking whether FFIO will be used... no > checking whether to skip C++, F77, or F90 APIs if compiler is broken... yes > checking whether examples should be built... yes > checking whether F77 API is desired... yes > checking whether any Fortran API is desired... yes > checking whether F90 API is desired... yes > checking whether fortran type sizes should be checked... yes > checking whether CXX API is desired... yes > checking whether v2 netCDF API should be built... yes > checking whether the ncgen/ncdump/nccopy 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 > configure: finding C compiler > checking for gcc... (cached) gcc > checking whether we are using the GNU C compiler... (cached) yes > checking whether gcc accepts -g... (cached) yes > checking for gcc option to accept ISO C89... (cached) none needed > checking dependency style of gcc... (cached) gcc3 > checking whether gcc and cc understand -c and -o together... yes > checking for an ANSI C-conforming const... yes > checking whether a CURLOPT_KEYPASSWD is defined... no > configure: finding Fortran compiler (will not be used if Fortran API is not > desired) > checking for gfortran... no > checking for g95... no > checking for xlf95... no > checking for f95... no > checking for fort... no > checking for ifort... no > checking for ifc... no > checking for efc... no > checking for pgfortran... no > checking for pgf95... no > checking for lf95... no > checking for ftn... no > checking for xlf90... no > checking for f90... no > checking for pgf90... no > checking for pghpf... no > checking for epcf90... no > checking for g77... no > checking for xlf... no > checking for f77... f77 > checking whether we are using the GNU Fortran compiler... yes > checking whether f77 accepts -g... yes > checking for f77... f77 > checking whether we are using the GNU Fortran 77 compiler... yes > checking whether f77 accepts -g... yes > configure: setting up Fortran 90 > checking what FC is set to... f77 > checking for Fortran flag to compile .f90 files... unknown > configure: error: Fortran could not compile .f90 files > > Thank you. > > -- > > Keerthi Priya Kasturi > PhD Research Scholar, > Civil Engineering Department > IIT Gandhinagar > > Russ Rew UCAR Unidata Program address@hidden http://www.unidata.ucar.edu Ticket Details =================== Ticket ID: BCT-221199 Department: Support netCDF Priority: Normal Status: Closed
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly 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.