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

[t-brown]

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

LIST OF MODIFIED FILES:

• 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.

[weiwangncar]

The regression test results:

Test Type              | Expected  | Received |  Failed
= = = = = = = = = = = = = = = = = = = = = = = =  = = = =
Number of Tests        : 23           24
Number of Builds       : 60           57
Number of Simulations  : 158           150        0
Number of Comparisons  : 95           86        0

Failed Simulations are: 
None
Which comparisons are not bit-for-bit: 
None

[smileMchen]

@t-brown
Please confirm that the following release note for this PR is correct:
The fortran library can be either hdf5_hl_fortran or hdf5hl_fortran for HDF5, which is now checked in Config.pl.

[t-brown]

Yeap, that's fine. Thanks.

[smileMchen]

@t-brown
Hi, Timothy
Thank you for the confirmation.