Fedora Account System
Red Hat Associate
Red Hat Customer
PETSc generates header files for Fortran automatically and puts them into the finclude directory. Those files are missing in newer package versions. Note: Files with the same name are available in the regular include dir, but they have a different content. Some background: I using the openSUSE Build Service to build DAMASK packages. https://build.opensuse.org/package/show/home:MarDieh/damask. DAMASK uses PETSc for two executables (damask_grid and damask_mesh). I could build for older Fedora versions (39 and 40), but now it fails. I believe that there was a transition to a more standard conforming file layout. In the old approach, it was sufficient to set PETSC_DIR (and leave PETSC_ARCH empty) to build damask_grid and damask_mesh. Is this still supposed to work, or are the requirements from Fedora on the file layout fundamentally different from what PETSc usually does? Reproducible: Always Steps to Reproduce: 1. Build a Fortran application using PETSc (here: damask_grid/damask_mesh) Actual Results: include files are not found Expected Results: Fedora PETSc packages should provide also Fortran include files Additional Information: I wanted to take the chance when updating the package to also provide an MPICH version. So far, only openMPI was supported. What is the correct approach to handle man files in that case? The executable has the same name in both cases, so the same files will be included in both packages.
FEDORA-2026-949166bd17 (petsc-3.25.3-3.fc45) has been submitted as an update to Fedora 45. https://bodhi.fedoraproject.org/updates/FEDORA-2026-949166bd17
FEDORA-2026-949166bd17 (petsc-3.25.3-3.fc45) has been pushed to the Fedora 45 stable repository. If problem still persists, please make note of it in this bug report.
thanks for the super fast fix. would it be possible to also update the Fedora 43 and/or 44 packages? I currently have only access to them.
(In reply to Martin Diehl from comment #3) > thanks for the super fast fix. Thank to you for this bug report. > > would it be possible to also update the Fedora 43 and/or 44 packages? I > currently have only access to them. Fixed packages will be in updates testing repositories soon: https://bodhi.fedoraproject.org/updates/?packages=petsc > Some background: I using the openSUSE Build Service to build DAMASK packages. https://build.opensuse.org/package/show/home:MarDieh/damask. DAMASK uses PETSc for two executables (damask_grid and damask_mesh). I > could build for older Fedora versions (39 and 40), but now it fails. I believe that there was a transition to a more standard conforming file layout. > In the old approach, it was sufficient to set PETSC_DIR (and leave PETSC_ARCH empty) to build damask_grid and damask_mesh. Is this still supposed to work, or are the requirements from Fedora on the file layout > fundamentally different from what PETSc usually does? I seen that on Fedora 43/44, PETSc currently provides `finclude` directory in a `petsc` sub-directory of `*/include/petsc` (too much useless sub-directory branches); in the recent fix, `finclude` in now moved in `*/include/petsc` By default, PETSc in Fedora sets PETSC_DIR=/usr, PETSC_ARCH can be set manually because `include` directory changes between petsc-devel and petsc-(openmpi or mpich)-devel. Anyway, CFLAGS are automatically set when you use pkgconfig files.
> Additional Information: > I wanted to take the chance when updating the package to also provide an MPICH version. So far, only openMPI was supported. What is the correct approach to handle man files in that case? The executable has the > same name in both cases, so the same files will be included in both packages. Are you talking of DAMASK?
(In reply to Antonio T. sagitter from comment #5) > > Additional Information: > > I wanted to take the chance when updating the package to also provide an MPICH version. So far, only openMPI was supported. What is the correct approach to handle man files in that case? The executable has the > same name in both cases, so the same files will be included in both packages. > > Are you talking of DAMASK? yes, do you know it? It is a split package with four packages, one provides the `damask_grid` executable (package `damask-grid`), the other `damask_mesh` (package `damask-mesh`). Note that currently capitalized and with symlink, but that does not matter. In 3.1.0 we also provide completion for shell (bash and zsh) and we also have man pages. Directories for man pages/tab completion are not per MPI-flavor if I understand it correctly. Hence, for a split, it is probably not possible to install damask-grid-openmpi and damask-grid-mpich at the same time because both want to install the same files.
I don't know openSUSE but in Fedora the MPI binaries, manpages likewise, are installed in dedicated directories: https://docs.fedoraproject.org/en-US/packaging-guidelines/MPI/#_packaging_of_mpi_compilers So, `damask_grid` executable goes in /usr/bin OpenMPI `damask_grid` executable goes in /usr/lib(64)/openmpi/bin MPICH `damask_grid` executable goes in /usr/lib(64)/mpich/bin manpages have dedicated directories: %{_mandir}/openmpi-%{_arch} and %{_mandir}/mpich-%{_arch}
thanks! I missed that. Then I'll be able to publish 3.1.0 soon.
I tried to build, but the following files are missing in comparison to my installation: Only in /opt/petsc/linux-c-opt/include/petsc/finclude: petscisbase.h Only in /opt/petsc/linux-c-opt/include/petsc/finclude: petscsysbase.h Only in /opt/petsc/linux-c-opt/include/petsc/finclude: petscvecbase.h
(In reply to Martin Diehl from comment #9) > I tried to build, but the following files are missing in comparison to my > installation: > > Only in /opt/petsc/linux-c-opt/include/petsc/finclude: petscisbase.h > Only in /opt/petsc/linux-c-opt/include/petsc/finclude: petscsysbase.h > Only in /opt/petsc/linux-c-opt/include/petsc/finclude: petscvecbase.h Okay. I'm adding them.
Please, check your builds with the release petsc-3.25.3-5.fc45 before i commit into all other branches.
Thanks! I now installed rawhide for testing. The files are in the package but in the wrong location. For MPICH and x86_64, they are in "usr/include/mpich-x86_64/petsc", but they should go into "usr/include/mpich-x86_64/petsc/finclude". The reason is that this path is hardcoded, "petscsys.h" for example has '#include "petsc/finclude/petscsysbase.h"'
Please, try the build release 0:3.25.3-6
works. Many thanks!
FEDORA-EPEL-2026-908bec402b (petsc-3.24.6-4.el10_3) has been submitted as an update to Fedora EPEL 10.3. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-908bec402b
FEDORA-2026-142eaaa7b2 (petsc-3.23.6-7.fc43) has been submitted as an update to Fedora 43. https://bodhi.fedoraproject.org/updates/FEDORA-2026-142eaaa7b2
FEDORA-2026-97fa2b34bc (petsc-3.24.6-3.fc44) has been submitted as an update to Fedora 44. https://bodhi.fedoraproject.org/updates/FEDORA-2026-97fa2b34bc
FEDORA-2026-97fa2b34bc has been pushed to the Fedora 44 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-97fa2b34bc` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-97fa2b34bc See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2026-908bec402b has been pushed to the Fedora EPEL 10.3 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-908bec402b See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2026-142eaaa7b2 has been pushed to the Fedora 43 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-142eaaa7b2` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-142eaaa7b2 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2026-908bec402b (petsc-3.24.6-4.el10_3) has been pushed to the Fedora EPEL 10.3 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2026-142eaaa7b2 (petsc-3.23.6-7.fc43) has been pushed to the Fedora 43 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2026-97fa2b34bc (petsc-3.24.6-3.fc44) has been pushed to the Fedora 44 stable repository. If problem still persists, please make note of it in this bug report.