Changing how Config.pl looks for the HDF5 high-level fortran library. (#1934)
commitd69761a6bcd542c911c23bb6225cae416c479dc7
authorTimothy Brown <t-brown@users.noreply.github.com>
Sun, 10 Dec 2023 02:26:45 +0000 (10 02:26 +0000)
committerGitHub <noreply@github.com>
Sun, 10 Dec 2023 02:26:45 +0000 (9 19:26 -0700)
tree9b3400464305c1a6cbd21ec3d911b9dc32d7589a
parenteaff759af7f8961b8605bd3488449042b9140a14
Changing how Config.pl looks for the HDF5 high-level fortran library. (#1934)

Changing how Config.pl looks for the HDF5 high-level fortran library.

TYPE: enhancement
KEYWORDS: HDF5, high-level, fortran, library

SOURCE: Timothy Brown (AWS)

DESCRIPTION OF CHANGES:
Problem:
Depending on the installation type (autotools or cmake) of HDF5 the high-level fortran library can be either `hdf5_hl_fortran` or `hdf5hl_fortran`.

Solution:
In `Config.pl` we now check the HDF5 library directory for the high-level fortran library.

ISSUE:
Fixes [manual WRF build with Spack](https://github.com/aws-samples/aws-hpc-tutorials/issues/452)

LIST OF MODIFIED FILES:
M      arch/Config.pl

TESTS CONDUCTED:
1. Yes. I have configured and built WRF against installs of HDF5 where the high-level fortran library has been
    a. hdf5_hl_fortran
    b. hdf5hl_fortran
    c. hdf5_hl_fortran and hdf5hl_fortran
2. Passed the Jenkins tests.

RELEASE NOTE: Config.pl now tests for the HDF5 high-level fortran library.
arch/Config.pl