Hi Lee, > I'm trying to build netcdf-4.1.3 with PGI compilers. I set env variables > as follows: > > export PATH=$PATH:/opt/pgi/linux86/9.0-4/bin > export PGI=/opt/pgi > export MANPATH=$MANPATH:$PGI/man > export LM_LICENSE_FILE=$PGI/license.dat > export CC=/opt/pgi/linux86/9.0-4/bin/pgcc > export FC=/opt/pgi/linux86/9.0-4/bin/pgf90 > export F90=/opt/pgi/linux86/9.0-4/bin/pgf90 > export CXX=/opt/pgi/linux86/9.0-4/bin/pgCC > export CPPFLAGS="-DpgiFortran" > export LD=/opt/pgi/linux86/9.0-4/bin/pgfortran > export > LD_LIBRARY_PATH=/lib:/usr/lib:/usr/local/lib:/opt/pgi/linux86/9.0-4/lib > export > INCLUDE=/usr/include:/usr/local/include:/opt/pgi/linux86/9.0-4/include > > When I run the configure script: > > ./configure --prefix=/usr/local --disable-netcdf-4 > > I get the following: > > > configure: netCDF 4.1.3 > checking build system type... i686-pc-linux-gnu > checking host system type... i686-pc-linux-gnu > checking target system type... i686-pc-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 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... no > 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... /opt/pgi/linux86/9.0-4/bin/pgcc > checking whether the C compiler works... no > configure: error: in `/home/wrf/netcdf/netcdf-4.1.3': > configure: error: C compiler cannot create executables > See `config.log' for more details > > Here is config.log: And here's the problem buried in the config.log output: > configure:4489: checking whether the C compiler works > configure:4511: /opt/pgi/linux86/9.0-4/bin/pgcc -DpgiFortran conftest.c > >&5 > pgi-cc-lin32: LICENSE MANAGER PROBLEM: No such feature exists. > Feature: pgi-cc-lin32 > License path: /opt/pgi/license.dat: > FLEXnet Licensing error:-5,357 > For further information, refer to the FLEXnet Licensing documentation, > available at "www.acresso.com". It would probably be best to debug the license manager problem on a small C program before trying i with netCDF-4.1.3. I'd also recommend the more recent netCDF-4.2 or even 4.2.1-rc1 if you encounter problems. --Russ Russ Rew UCAR Unidata Program address@hidden http://www.unidata.ucar.edu Ticket Details =================== Ticket ID: BOZ-597307 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.