-
-
Notifications
You must be signed in to change notification settings - Fork 281
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
[BUG] HDF5 C++ 1.14.0 includes H5FDsubfiling build path #2621
Labels
Component - Build
CMake, Autotools
Priority - 2. Medium ⏹
It would be nice to have this in the next release
Type - Bug / Bugfix
Please report security issues to [email protected] instead of creating an issue on GitHub
Comments
This is likely the same as in #2422 |
jhendersonHDF
added a commit
to jhendersonHDF/hdf5
that referenced
this issue
Apr 5, 2023
lrknox
pushed a commit
that referenced
this issue
Apr 11, 2023
jhendersonHDF
added a commit
to jhendersonHDF/hdf5
that referenced
this issue
Apr 13, 2023
brtnfld
pushed a commit
to brtnfld/hdf5
that referenced
this issue
Apr 13, 2023
byrnHDF
pushed a commit
to byrnHDF/hdf5
that referenced
this issue
Apr 16, 2023
brtnfld
pushed a commit
to brtnfld/hdf5
that referenced
this issue
May 17, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Component - Build
CMake, Autotools
Priority - 2. Medium ⏹
It would be nice to have this in the next release
Type - Bug / Bugfix
Please report security issues to [email protected] instead of creating an issue on GitHub
Describe the bug
Using HDF5 C++ library with cmake results in error:
The path is from HDF5 build directory which is deleted after install
Expected behavior
No build path should be included anywhere, because H5FDsubfiling headers are already installed in the system.
Platform (please complete the following information)
./configure --prefix=/usr/local --enable-cxx
Additional context
Path to H5FDsubfiling is included in 3 places:
Removing flags from h5c++ and h5cc fixes the problem.
The text was updated successfully, but these errors were encountered: