Mark,
Yesterday, I wrote:
> First I built and installed HDF5 with --prefix=${H5DIR}.
> Then I built and installed HDF4 with
>
> ./configure --enable-shared --disable-netcdf --disable-fortran
> --prefix=${H4DIR}
> make
> make install
>
> Then for netCDF-4.1.3 (and this probably works for later versions as well), I
> used
>
> CPPFLAGS="-I${H5DIR}/include -I${H4DIR}/include -I/opt/include"
> LDFLAGS="-L${H5DIR}/lib -L${H4DIR}/lib -L/opt/lib" ./configure
> --disable-shared --enable-hdf4 --enable-hdf4-file-tests
>
> and make check completed with no errors. It also worked fine with
> "--disable-dap",
> but I had the necessary libcurl previously installed in /opt/lib, so I
> verified that
> it works with DAP client access. The HDF-4 file tests also completed
> successfully.
I was curious whether the "--disable-shared" for the netCDF build that enabled
HDF4
access was really needed. It turns out that it's not. Everything builds and
the tests
run successfully in both netCDF 4.1.3 and the current 4.3.0 release candidate
when
built as a shared library, as long as HDF4 is built with "--disable-netcdf".
--Russ
Russ Rew UCAR Unidata Program
address@hidden http://www.unidata.ucar.edu
Ticket Details
===================
Ticket ID: VOG-153523
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.