Bug 2336249 - Macaulay2 fails to build with GCC 15 (-Wtemplate-body)
Summary: Macaulay2 fails to build with GCC 15 (-Wtemplate-body)
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: Macaulay2
Version: 42
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Rex Dieter
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: gcc-15-mass-prebuild
TreeView+ depends on / blocked
 
Reported: 2025-01-07 21:26 UTC by Dave Malcolm
Modified: 2025-03-15 00:27 UTC (History)
2 users (show)

Fixed In Version: Macaulay2-1.24.11-1.fc42
Clone Of:
Environment:
Last Closed: 2025-03-15 00:27:35 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Dave Malcolm 2025-01-07 21:26:46 UTC
I'm experimentally rebuilding rawhide with the not-yet-released GCC 15 to see if anything breaks, and to help write the porting guide.  See https://fedoraproject.org/wiki/User:Dmalcolm/gcc-15

My test build with GCC 15 failed:
https://copr.fedorainfracloud.org/coprs/dmalcolm/gcc-15-smoketest-3.failed/build/8476036/

whereas my test build with GCC 14 succeeded:
https://copr.fedorainfracloud.org/coprs/dmalcolm/gcc-15-smoketest-3.failed.checker/build/8477629/

Looking at the failure logs e.g.
https://download.copr.fedorainfracloud.org/results/dmalcolm/gcc-15-smoketest-3.failed/fedora-rawhide-x86_64/08476036-Macaulay2/builder-live.log.gz
I see:

In file included from /usr/include/recint/rdiv.h:48,
                 from /usr/include/recint/rint.h:53,
                 from /usr/include/givaro/modular-ruint.h:24,
                 from /usr/include/givaro/modular.h:26,
                 from ../../linbox/field/field-traits.h:30,
                 from ../../linbox/solutions/methods.h:25,
                 from ../../linbox/algorithms/rational-solver.h:41,
                 from ../../linbox/algorithms/diophantine-solver.h:29,
                 from diophantine-solver.C:26:
/usr/include/recint/rfiddling.h: In static member function 'static RecInt::rint<K> RecInt::rint<K>::maxFFLAS()':
/usr/include/recint/rfiddling.h:170:29: error: 'class RecInt::rint<K>' has no member named 'Low' [-Wtemplate-body]
  170 |         set_highest_bit(max.Low.Value);
      |                             ^~~

See https://fedoraproject.org/wiki/User:Dmalcolm/gcc-15#C++:_error_with_-Wtemplate-body for notes.

Reproducible: Didn't try

Comment 1 Fedora Update System 2025-02-21 11:53:01 UTC
FEDORA-2025-4e0c65ee4e (fflas-ffpack-2.5.0-14.fc43, givaro-4.2.1-1.fc43, and 3 more) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-4e0c65ee4e

Comment 2 Fedora Update System 2025-02-21 11:53:24 UTC
FEDORA-2025-adb5d17204 (fflas-ffpack-2.5.0-14.fc42, givaro-4.2.1-1.fc42, and 3 more) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-adb5d17204

Comment 3 Fedora Update System 2025-02-21 12:05:49 UTC
FEDORA-2025-4e0c65ee4e (fflas-ffpack-2.5.0-14.fc43, givaro-4.2.1-1.fc43, and 3 more) has been pushed to the Fedora 43 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 4 Fedora Update System 2025-02-22 03:17:20 UTC
FEDORA-2025-adb5d17204 has been pushed to the Fedora 42 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-adb5d17204`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-adb5d17204

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 5 Aoife Moloney 2025-02-26 13:21:33 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 42 development cycle.
Changing version to 42.

Comment 6 Fedora Update System 2025-03-15 00:27:35 UTC
FEDORA-2025-adb5d17204 (fflas-ffpack-2.5.0-14.fc42, givaro-4.2.1-1.fc42, and 3 more) has been pushed to the Fedora 42 stable repository.
If problem still persists, please make note of it in this bug report.


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