FTBFS with GCC-14 (rebuild against mpi-defaults 1.17)

Bug #2075261 reported by Erich Eickmeyer
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
aces3 (Debian)
New
Unknown
aces3 (Ubuntu)
New
Undecided
Unassigned
adios (Debian)
Fix Released
Unknown
adios (Ubuntu)
Fix Released
Undecided
Unassigned
ampliconnoise (Debian)
Fix Released
Unknown
ampliconnoise (Ubuntu)
New
Undecided
Unassigned
apbs (Debian)
New
Unknown
apbs (Ubuntu)
New
Undecided
Unassigned
fenics-dolfinx (Debian)
New
Unknown
fenics-dolfinx (Ubuntu)
New
Undecided
Unassigned
fftw (Debian)
Fix Released
Unknown
fftw (Ubuntu)
Fix Released
Undecided
Unassigned
gerris (Debian)
New
Unknown
gerris (Ubuntu)
New
Undecided
Unassigned
hdf5 (Debian)
Fix Released
Unknown
hdf5 (Ubuntu)
New
Undecided
Unassigned
hypre (Debian)
Fix Released
Unknown
hypre (Ubuntu)
Fix Released
Undecided
Unassigned
mpb (Debian)
Fix Released
Unknown
mpb (Ubuntu)
Fix Released
Undecided
Unassigned
mpqc (Debian)
New
Unknown
mpqc (Ubuntu)
New
Undecided
Unassigned
prime-phylo (Debian)
Fix Released
Unknown
prime-phylo (Ubuntu)
Fix Released
Undecided
Unassigned
ruby-mpi (Ubuntu)
New
Undecided
Unassigned
scalapack (Debian)
Fix Released
Unknown
scalapack (Ubuntu)
New
Undecided
Unassigned
scotch (Debian)
Fix Released
Unknown
scotch (Ubuntu)
New
Undecided
Unassigned
silo-llnl (Debian)
Fix Released
Unknown
silo-llnl (Ubuntu)
New
Undecided
Unassigned
sopt (Debian)
Confirmed
Unknown
sopt (Ubuntu)
New
Undecided
Unassigned
spooles (Debian)
New
Unknown
spooles (Ubuntu)
New
Undecided
Unassigned
sundials (Debian)
New
Unknown
sundials (Ubuntu)
New
Undecided
Unassigned
tree-puzzle (Debian)
Confirmed
Unknown
tree-puzzle (Ubuntu)
New
Undecided
Unassigned

Bug Description

Following a no-change rebuild against mpi-defaults 1.17, these packages completely FTBFS on all architectures.

This appears to be due to GCC-14.

See individual package builds for more details.

Changed in apbs (Ubuntu):
assignee: nobody → Olivier Gayot (ogayot)
description: updated
Changed in gerris (Ubuntu):
assignee: nobody → Olivier Gayot (ogayot)
Changed in ampliconnoise (Ubuntu):
assignee: nobody → Olivier Gayot (ogayot)
description: updated
description: updated
Revision history for this message
Erich Eickmeyer (eeickmeyer) wrote :

Strangely, fftw does *not* fail on armhf, though it does fail on all other archs.

Changed in fftw (Ubuntu):
assignee: nobody → Olivier Gayot (ogayot)
Olivier Gayot (ogayot)
summary: - FTBFS against mpi-defaults 1.17
+ FTBFS with GCC-14 (rebuild against mpi-defaults 1.17)
Changed in aces3 (Ubuntu):
assignee: Olivier Gayot (ogayot) → nobody
Changed in ampliconnoise (Ubuntu):
assignee: Olivier Gayot (ogayot) → nobody
Changed in apbs (Ubuntu):
assignee: Olivier Gayot (ogayot) → nobody
Changed in fftw (Ubuntu):
assignee: Olivier Gayot (ogayot) → nobody
Changed in gerris (Ubuntu):
assignee: Olivier Gayot (ogayot) → nobody
Changed in fftw (Debian):
status: Unknown → New
Changed in gerris (Debian):
status: Unknown → New
Changed in ampliconnoise (Debian):
status: Unknown → New
Changed in apbs (Debian):
status: Unknown → New
Revision history for this message
Erich Eickmeyer (eeickmeyer) wrote :

Similarly to fftw, hypre also ftbfs !armhf

description: updated
Changed in adios (Debian):
status: Unknown → New
Changed in hdf5 (Debian):
status: Unknown → Fix Released
Changed in hypre (Debian):
status: Unknown → New
Changed in mpqc (Debian):
status: Unknown → New
Changed in mpb (Debian):
status: Unknown → New
no longer affects: murasaki (Ubuntu)
no longer affects: phyml (Ubuntu)
Changed in fenics-dolfinx (Debian):
status: Unknown → New
no longer affects: slepc (Ubuntu)
no longer affects: stopt (Ubuntu)
no longer affects: ruby-mpi (Ubuntu)
Revision history for this message
Erich Eickmeyer (eeickmeyer) wrote :

Re-added ruby-mpi since there is, indeed, some weird gcc madness going on there.

Changed in prime-phylo (Debian):
status: Unknown → New
Changed in scalapack (Debian):
status: Unknown → Fix Released
Changed in scotch (Debian):
status: Unknown → Confirmed
Changed in silo-llnl (Debian):
status: Unknown → New
Changed in sopt (Debian):
status: Unknown → Confirmed
Changed in spooles (Debian):
status: Unknown → New
Changed in sundials (Debian):
status: Unknown → New
Changed in tree-puzzle (Debian):
status: Unknown → New
Changed in fftw (Debian):
status: New → Fix Released
Changed in aces3 (Debian):
status: Unknown → New
Changed in hypre (Debian):
status: New → Confirmed
Changed in mpb (Debian):
status: New → Fix Released
Changed in mpb (Ubuntu):
status: New → Fix Released
Changed in fftw (Ubuntu):
status: New → Fix Released
Changed in hypre (Debian):
status: Confirmed → Fix Released
Revision history for this message
Erich Eickmeyer (eeickmeyer) wrote :

This bug was fixed in the package hypre - 2.31.0-1exp2

---------------
hypre (2.31.0-1exp2) experimental; urgency=medium

  * debian patch build_gcc14_PR1110.patch applies upstream PR#1110 to
    enable build using gcc-14. Closes: #1075077.

 -- Drew Parsons <email address hidden> Sun, 04 Aug 2024 11:17:02 +0200

hypre (2.31.0-1exp1) experimental; urgency=medium

  * New upstream release. New ABI 2.31.0.
    - applies debian patches fix_make_check.patch,
      no_timings_finalizeAllTimings.patch
    - obsoletes debian patch test.patch (scripts now use bash)
  * add Drew Parsons as uploader

 -- Drew Parsons <email address hidden> Sat, 20 Jul 2024 14:00:52 +0200

Changed in hypre (Ubuntu):
status: New → Fix Released
Revision history for this message
Erich Eickmeyer (eeickmeyer) wrote :

For scalapack: the solution? Use GCC-13 or older per https://github.com/Reference-ScaLAPACK/scalapack/issues/97. (obviously not an option)

Changed in ampliconnoise (Debian):
status: New → Fix Released
Changed in prime-phylo (Debian):
status: New → Fix Released
Changed in tree-puzzle (Debian):
status: New → Confirmed
Changed in silo-llnl (Debian):
status: New → Fix Released
Changed in scotch (Debian):
status: Confirmed → Fix Released
Changed in adios (Debian):
status: New → Fix Released
Changed in adios (Ubuntu):
status: New → Fix Released
Changed in prime-phylo (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.