-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HDF5 1.12.0 compatibility #104
Comments
Hi @kelbstf Configuration of rhdf5 is pretty tied to the Rhdf5lib package and the 1.10.7 version of the library distributed with that. This design decision was deliberately taken to try and simplify the installation of HDF5 for users and to tie the package to a single version of HDF5 to make debugging easier for developers. It's pretty hard (probably impossible) to override that at the moment. However at some point I did consider this, and you can set the environment variable |
Hi @grimbough,, thank you very much for looking into this, i really appreciate it.
I guess this relates to "szlib" and how 1.10.7 has been compiled? Before i am digging deeper in this direction: Would the R package management be able to keep track of those implicit, "2nd-level" compatibility issues? This might be hard to handle on a multiuser server... |
Hello @grimbough,
is there any option to compile rhdf5 against HDF5 1.12.0 instead of HDF5 1.10.x(7) (in R 4.x)?
Our stack makes heavy use of HDF5 1.12.0 and it would be a blessing to simply add "/rhdf5" to that same stack, using that same HDF5 1.12.0.
This would spare running multiple R-(Server)versions per HDF5 interface in a multiuser environment.
HDFGroup hints that one could compile applications against HDF5 1.12.0, but on a 1.10.x feature set level, as described here [https://www.hdfgroup.org/downloads/hdf5], but i am not shure whether this would possibly harm the integrity of "rhdf5".
Not to mention i currently would not know how to provide the described build options to the compiler from within R?
Best regards
The text was updated successfully, but these errors were encountered: