Bug 1971826 - h5fc can't find module files
Summary: h5fc can't find module files
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: hdf5
Version: 34
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Orion Poplawski
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-06-14 19:58 UTC by John Haiducek
Modified: 2022-06-08 00:25 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2022-06-08 00:25:08 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description John Haiducek 2021-06-14 19:58:56 UTC
Description of problem:

h5fc is unuseable


Version-Release number of selected component (if applicable):

1.10.6-5


How reproducible:

Every time

Steps to Reproduce:
1. Attempt to compile a Fortran file that imports one or more hdf5 modules with h5fc

Actual results:

h5fc gives the error:

[code]
Fatal Error: Cannot open module file ‘hdf5.mod’ for reading at (1): No such file or directory
compilation terminated.
[/code]

Expected results:

h5fc should compile the file

Additional info:

Output from `rpm -ql` indicates that the module files are installed in /usr/lib64/gfortran/modules
[code]
$ rpm -ql hdf5-devel

/snip/

/usr/lib64/gfortran/modules/h5_gen.mod
/usr/lib64/gfortran/modules/h5a.mod
/usr/lib64/gfortran/modules/h5d.mod
/usr/lib64/gfortran/modules/h5ds.mod
/usr/lib64/gfortran/modules/h5e.mod
/usr/lib64/gfortran/modules/h5f.mod
/usr/lib64/gfortran/modules/h5fortkit.mod
/usr/lib64/gfortran/modules/h5fortran_types.mod
/usr/lib64/gfortran/modules/h5g.mod
/usr/lib64/gfortran/modules/h5global.mod
/usr/lib64/gfortran/modules/h5i.mod
/usr/lib64/gfortran/modules/h5im.mod
/usr/lib64/gfortran/modules/h5l.mod
/usr/lib64/gfortran/modules/h5lib.mod
/usr/lib64/gfortran/modules/h5lt.mod
/usr/lib64/gfortran/modules/h5lt_const.mod
/usr/lib64/gfortran/modules/h5o.mod
/usr/lib64/gfortran/modules/h5p.mod
/usr/lib64/gfortran/modules/h5r.mod
/usr/lib64/gfortran/modules/h5s.mod
/usr/lib64/gfortran/modules/h5t.mod
/usr/lib64/gfortran/modules/h5tb.mod
/usr/lib64/gfortran/modules/h5tb_const.mod
/usr/lib64/gfortran/modules/h5z.mod
/usr/lib64/gfortran/modules/hdf5.mod

/snip/

[/code]

But `h5fc -show` indicates that it is looking for gfortran module files in /usr/include:
[code]
$ h5fc -show
gfortran -I/usr/include -L/usr/lib64 -lhdf5hl_fortran -lhdf5_hl -lhdf5_fortran -lhdf5
[/code]

h5fc should be configured to add -I/usr/lib64/gfortran/modules to the compiler command line, or the module files should be installed to /usr/include.

Comment 1 Ben Cotton 2022-05-12 16:21:32 UTC
This message is a reminder that Fedora Linux 34 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '34'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 34 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 2 Ben Cotton 2022-06-08 00:25:08 UTC
Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07.

Fedora Linux 34 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.