unpushed

glibc-2.41-2.fc42

FEDORA-2025-ea17c6d914 created by fweimer 2 months ago for Fedora 42

This update addresses an issue where building on Fedora 42 may result in binaries that do not run correctly on earlier glibc versions, related to the use of PTHREAD_COND_INITIALIZER (swbz#32786).

This update also includes changes from the glibc's 2.41 stable release branch. Noteworthy fixes are:

  • String and math function enhancements using Scalabe Vector Extensions (SVE) on AArch64
  • Improved <math.h> compatibility for historic Clang versions
  • Reliable support for gp optimization and IRELATIVE relocations on RISC-V

This update has been submitted for testing by fweimer.

2 months ago

This update's test gating status has been changed to 'waiting'.

2 months ago

This update's test gating status has been changed to 'waiting'.

2 months ago

This update's test gating status has been changed to 'failed'.

2 months ago

I forgot that Fedora 42 uses GCC 15, too. Same regression as in the rawhide update: FEDORA-2025-6616d58c7a

Yeah. We should probably have stopped the F42 gcc update going stable :( too late now.

There's a new snapshot for F43, btw - could try with that and see if the bug happened to get fixed upstream?

The problematic GCC commit has been reverted upstream and reimplemented in a completely different way. The crash is gone. We'll do a glibc rawhide sync from upstream glibc, using the new GCC snapshot soon.

There was a new GCC build 7+ days ago. If this GCC snapshot resolves the problem could we get glibc updated?

@davidlt Aren't we in the release freeze now? I suppose I could prepare a Fedora 42 update and have it wait in the queue.

Yes, we are in a freeze. All the updates marked for "stable" are pooling up as day 1 updates.

I personally interested in pulling a new glibc into Fedora/RISC-V 42 builds, which don't follow Bodhi, etc. As soon as there is NVR in Koji, I could pull it in.


Please login to add feedback.

Metadata
Type
unspecified
Karma
0
Content Type
RPM
Test Gating
Autopush Settings
Unstable by Karma
-3
Stable by Karma
3
Stable by Time
3 days
Thresholds
Minimum Karma
+2
Minimum Testing
14 days
Dates
submitted
2 months ago

Automated Test Results