id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
393	ROPP8.0 dependency issues	Ian Culverwell	Dave Offiler Ian Culverwell	"ROPP8.0 beta reviewer Dave Offiler (UKMO) says
{{{
This is where the 'fun' starts. The netCDF ./configure fails to locate the 
statically-built HDF5 libraries, whatever combination of flags I tried in the
netcdf4_configure_ifort_linux (or other compiler) mini-script to point it to
$PREFIX/lib64 (NB prefix/lib64 on OpenSUSE, not prefix/lib).

So tried re-building HDF5 as shared (simply change --disable-shared to 
--enable-shared) which got netCDF4 ./configure going. However, since HDF5 libs
are in a non-standard location, LD_LIBRARY_PATH needs this extra path for
run-time shared-lib location. This could be added to the mini-script(s) for the
build testing, but users woud stil have to set it (e.g. in their .profile) 
before running any tools accessing any (ROPP or EUM) netCDF files.

But then HDF5 barfs on finding my system-installed HDF5 .h file (v1.8.12) 
before the local one, and this is inconsistent with the local HDF5 libs 
(1.8.14). This causes netCDF reading tools to fail (reporting it as not a 
netCDF file).

Will try later with a local build of HDF5 v1.8.12....

NB: in principle it should be possible for netCDF to pick up a system-installed
HDF5, except that ROPP ./configure wants the Fortran API (which exists but only
a gfortran pre-built one). Not sure why, as the F90-API isn't used by ROPP 
otherwise. Can the ROPP_IO ./configure drop the 'requirement' for HDF5-Fortran
so as to allow a system-installed C-lib to be used?
}}}

Is this anything to do with ROPP?"	defect	closed	normal	9.0	External deps	7.1	wontfix