-
Notifications
You must be signed in to change notification settings - Fork 0
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 build error (VEGA) #4
Comments
What HDF5 version do you have in cmake/libraries.json? Line 68 in 7274e75
You can put like 1_10_6, 1_10_7, 1_12_1, to see if there is a working version. HDF Group has been overhauling build of HDF5. 1_12_2 was supposed to fix a number of substantial HDF5 build problems and boost HDF5 performance, but maybe they broke something for older systems. I.e. what HDF5 version are you now trying to build? If before 1_12_2 maybe With older HDF5 versions, there were other build issues I saw, but the error you noted is not an error I've seen yet. |
So I updated to cmake 3.23.2 and that seemed to not trigger the same error but now I get this:
|
I just realized that this is now an issue with h5fortran apparently... How do I set the version for that; does it make sense to try an earlier version since this did work before. |
Okay I found a workaround for VEGA (gcc 8.3). It's a two part process:
|
@scivision Could you take a look at this and see if you can reproduce with gcc 8.3? |
[pineyrob@vegaln1 GEMININEWEST3]$ module list
-- The following features have been disabled:
-- Configuring done
-- Build files have been written to: /scratch/pineyrob/GEMININEWEST3/external/build/zlib-prefix/src/zlib-build -- Configuring incomplete, errors occurred! |
@paulinchin I think this issue is resolved now? It was a general issue with blanking out unwanted environment variables on Vega? |
However, there may still be an issue with h5fortran > v4.4.4, but not the more severe issue shown later |
I confirm on CentOS 7 with GCC 8.3.0 that the compiler bug where
is still present in h5fortran main branch. I will move that part to h5fortran repo. |
I am closing this as the GCC 8.3.0 workaround is implemented in a new version of h5fortran. This is a definite GCC 8.3.0 bug that was fixed by GCC 8.5.0. The rest of the reported issues here were resolved by clearing out unwanted compiler environment variables on Vega. |
gcc 8.3 and cmake 3.20:
The text was updated successfully, but these errors were encountered: