FS#49212 - [hdf5] 1.10.0 not compatible with certain tools
Attached to Project:
Arch Linux
Opened by Ejner Fergo (numasan) - Wednesday, 04 May 2016, 17:27 GMT
Last edited by Doug Newgard (Scimmia) - Sunday, 20 November 2016, 19:43 GMT
Opened by Ejner Fergo (numasan) - Wednesday, 04 May 2016, 17:27 GMT
Last edited by Doug Newgard (Scimmia) - Sunday, 20 November 2016, 19:43 GMT
|
Details
Since HDF5 1.10.0 made changes to the API, some tools (eg.
https://github.com/alembic) breaks and can't compile.
Please configure package with: --with-default-api-version=v18 or continue to provide the old 1.8.x package. Also, configure option --enable-linux-lfs is unrecognized and --with-pthread=DIR is ignored since --enable-threadsafe is off by default. Thanks. |
This task depends upon
Closed by Doug Newgard (Scimmia)
Sunday, 20 November 2016, 19:43 GMT
Reason for closing: Implemented
Additional comments about closing: hdf5_18 is in Extra (for now).
Sunday, 20 November 2016, 19:43 GMT
Reason for closing: Implemented
Additional comments about closing: hdf5_18 is in Extra (for now).
I'm not an expert in HDF5, so don't know what it will affect, but there must be a reason they put the --with-default-api-version=v18 configure option in version 1.10.0
Regarding the other configure options, I still think they should be looked at (enabling threadsafe), so I won't request a closure just yet.
About threadsafe, it is now incompatible with the high level library which I don't think we would want to disable (I think it may even be needed for netcdf, but could be wrong here). What I might do is rename the hdf5-cpp-fortran package to hdf5 (which should be possible now that we don't have threadsafe anymore), and introduce a hdf5-threadsafe package. Would that work for you?
As is evident from my previous comments, I'm not qualified to provide an opinion, as I don't know what does and doesn't need thread safety or high level libraries, and why it is mutually exclusive. I trust your judgement.
It turns out thread safety *is* important for Alembic, and the developers will look into if the high-level option is necessary for that library. So your suggestion on introducing a hdf5-threadsafe package sounds like the best solution.
It could potentially use the --enable-unsupported option to allow both threadsafe and hl to be used, effectively making it work like 1.8.15, but I understand if this is not something you want.
I had to downgrade hdf and pytables per the first github issue link I've posted
I can report that Alembic devs have removed dependence on hdf5_hl and the lib is also compatible with hdf5-1.10.0 now. Will you build hdf5 with same options as hdf5_18 (--disable-hl --enable-threadsafe) or is netcdf still depended on hl? I hope not, since it is now a dependency of ffmpeg. If it is, would you consider building hdf5 with the --enable-unsupported option?