Bug 2524375
| Summary: | petsc-devel and petsc64-devel do not ship petsc/mpiuni headers | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Ali Erdinc Koroglu <ali.koroglu> |
| Component: | petsc | Assignee: | Antonio T. sagitter <sagitterghostproton.me> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rawhide | CC: | sagitterghostproton.me |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | petsc-3.24.6-5.el10_4 petsc-3.23.6-8.fc43 petsc-3.24.6-4.fc44 petsc-3.25.4-2.fc45 | Doc Type: | --- |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2026-09-05 00:26:29 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 2507022 | ||
Could you please review my PR for this fix : https://src.fedoraproject.org/rpms/petsc/pull-request/11 FEDORA-2026-27422b4f76 (petsc-3.24.6-4.fc44) has been submitted as an update to Fedora 44. https://bodhi.fedoraproject.org/updates/FEDORA-2026-27422b4f76 FEDORA-2026-fec1533d95 (petsc-3.25.4-2.fc45) has been submitted as an update to Fedora 45. https://bodhi.fedoraproject.org/updates/FEDORA-2026-fec1533d95 FEDORA-2026-511c212155 (petsc-3.23.6-8.fc43) has been submitted as an update to Fedora 43. https://bodhi.fedoraproject.org/updates/FEDORA-2026-511c212155 FEDORA-2026-511c212155 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-511c212155` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-511c212155 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-EPEL-2026-79786c5fd4 has been pushed to the Fedora EPEL 10.4 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-79786c5fd4 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2026-27422b4f76 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-27422b4f76` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-27422b4f76 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2026-fec1533d95 has been pushed to the Fedora 45 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-fec1533d95` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-fec1533d95 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-EPEL-2026-79786c5fd4 (petsc-3.24.6-5.el10_4) has been pushed to the Fedora EPEL 10.4 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2026-511c212155 (petsc-3.23.6-8.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-27422b4f76 (petsc-3.24.6-4.fc44) has been pushed to the Fedora 44 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2026-fec1533d95 (petsc-3.25.4-2.fc45) has been pushed to the Fedora 45 stable repository. If problem still persists, please make note of it in this bug report. |
The serial (petsc) and 64-bit-integer (petsc64) flavours are configured with --with-mpi=0, so PETSC_HAVE_MPIUNI is defined in petscconf.h and petscsys.h unconditionally does: #include <petsc/mpiuni/mpi.h> That directory is not staged into the buildroot for either flavour, so including any PETSc header against petsc-devel or petsc64-devel fails. Version-Release number of selected component (if applicable): petsc-3.25.4-1.fc45 (and rawhide) Reproducible: Always Steps to Reproduce: 1. dnf install petsc-devel 2. echo '#include <petsc.h>' > t.c 3. gcc -I/usr/include/petsc -c t.c Actual Results: /usr/include/petsc/petscsys.h:122:12: fatal error: petsc/mpiuni/mpi.h: No such file or directory Expected Results: Compiles. Additional Information: Upstream installs the mpiuni headers exactly when the build uses MPIUni (config/install.py, installIncludes): if not self.mpi.usingMPIUni: exclude.append('mpiuni') The spec hand-copies the include tree instead of using upstream's install target, and has the rule inverted: mpiuni is copied into the two --with-mpi=1 flavours, which never use it, and omitted from the two --with-mpi=0 flavours, which require it. From the petsc-3.25.4-1.fc45 x86_64 build.log: 2534 configure --with-mpi=0 -> 2959 Using mpi.h: mpiuni 4707 configure --with-mpi=0 -> 5129 Using mpi.h: mpiuni 6992 configure --with-mpi=1 -> 7476 Using mpi.h: .../openmpi-x86_64/mpi.h 9652 configure --with-mpi=1 -> 10158 Using mpi.h: .../mpich-x86_64/mpi.h 12391 cp -a include/petsc/mpiuni .../usr/include/openmpi-x86_64/petsc/ 12712 cp -a include/petsc/mpiuni .../usr/include/mpich-x86_64/petsc/ with no copy to %{_includedir}/petsc/ or %{_includedir}/petsc64/. This currently causes an FTBFS in getdp-3.6.0-17.fc46.