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

[netCDF #KBE-868074]: netCDF build error

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: [netCDF #KBE-868074]: netCDF build error
  • Date: Tue, 20 Sep 2016 11:01:25 -0600
Hello,

This is a normal failure you would expect to see; configure looks for several 
different hdf5 libraries, including hdf5dll, and uses the first one it finds.  
For example, it will also look for libhdf5.  So, the failure you are seeing is 
not in-and-of-itself a problem.  What is the larger issue you are seeing? If 
you provide the `config.log` file generated when you run configure, I would be 
happy to take a look at it.

Thank you,

-Ward

> Hi netCDF folks,
> 
> When I tried to build netCDF 4.1.3 from a customer, I got the following error 
> in config.log.:
> 
> configure:26911: icc -o conftest -g -O2   conftest.c -lhdf5dll  -lm -lz 
> -lcurl  >&5
> ld: cannot find -lhdf5dll
> 
> Here's my configure command line:
> 
> ./configure --enable-netcdf-4 
> --with-hdf5=/gbc-lustre/cho/MoES/ROMS/hdf5-1.8.11 
> --with-zlib=/gbc-lustre/cho/MoES/ROMS/zlib-1.2.8 
> --prefix=/gbc-lustre/cho/MoES/ROMS/netcdf-4.1.3
> 
> I looked in hdf5 lib directory, and I don't find this library either.
> 
> Any idea what am I missing here?
> 
> Thanks in advance!
> 
> --
> 
> Kah-Song
> ==================
> Kah-Song Cho
> SGI HPC Benchmarking
> Tel: 714-368-5960
> ==================
> 
> 
> 


Ticket Details
===================
Ticket ID: KBE-868074
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.