You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to suggest that instead of using a specific compiler in the Makefile we use the h5pfc (Fortran) and h5pcc (C) compiler wrappers. This negates the need for the $HDF5 link line and should make compilation easier for many people.
The text was updated successfully, but these errors were encountered:
On Sep 17, 2020, at 5:26 PM, Samuel Lazerson ***@***.***> wrote:
I would like to suggest that instead of using a specific compiler in the Makefile we use the h5pfc (Fortran) and h5pcc (C) compiler wrappers. This negates the need for the $HDF5 link line and should make compilation easier for many people.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub, or unsubscribe.
@lazersos I just found that the easiest thing to compile the code on Draco is to set FC=mpiifort (as the one on Eddy). Nothing needs to be changed with HDF5. Is this related to your suggestion?
@zhucaoxiang No the idea is that if you use h5fc or h5pfc then you're using the wrappered compilers and then don't need to worry about passing the compiler or linker flags (or paths).
I would like to suggest that instead of using a specific compiler in the Makefile we use the h5pfc (Fortran) and h5pcc (C) compiler wrappers. This negates the need for the
$HDF5
link line and should make compilation easier for many people.The text was updated successfully, but these errors were encountered: