#7907 Fedora 30 Toolchain Rebase: glibc 2.29, gcc 9.0
Closed: Fixed a year ago by pbrobinson. Opened 2 years ago by codonell.

  • Describe the issue

All Fedora releases must be released using a released and supported version of the core toolchain involving glibc, gcc, and binutils.

The Fedora toolchain team is responsible for ensuring that Fedora Rawhide stabilizes static linking, code generation, and library ABI, before a Fedora release, or that after the branch that the Fedora release is rebased (a very small rebase) to the final released version. This is a requirement for Fedora to inherit the ABI and API guarantees provided by upstream. If a mass rebuild is required by binutils, gcc, glibc or other components, the Fedora toolcahin team will ensure coordination with release engineering such that a mass rebuild uses the released version of all components and fix any last minute ABI or code-generation changes.

  • When do you need this? (2019/01/30)

We need a mass rebuild.

Change page for review: https://fedoraproject.org/wiki/Changes/GLIBC229
Owner: Carlos O'Donell carlos@redhat.com
glibc mass rebuild request: This request.

Change page for review: https://fedoraproject.org/wiki/Changes/PPC64LE_Float128_Transition
Owner: Carlos O'Donell carlos@redhat.com
glibc mass rebuild request: ppc64le transition to 128-bit IEEE long double.

GCC will file a system-wide change request for GCC 9 transition also in December.

Binutils will remain as 2.31.1 and will not change (Nick Clifton's notes).

  • If we cannot complete your request, what is the impact?

I we cannot do a mass rebuild then we should not transition to glibc 2.29 or gcc 9, but we might still be able to transition via targeted mass rebuilds.


Metadata Update from @mohanboddu:
- Issue tagged with: change-ack, changes, f30, mass rebuild

2 years ago

RelEng acks the change and will run a mass rebuild.

The ppc64le float128 transition is not happening.
I'm removing it from the list of accepted changes.

Metadata Update from @syeghiay:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

2 years ago

Metadata Update from @codonell:
- Issue status updated to: Open (was: Closed)

a year ago

Sorry, please close this out, I accidentally reopened. I'm filling a new ticket for the F33 mass rebuild.

Metadata Update from @pbrobinson:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

a year ago

Login to comment on this ticket.

Metadata