On Fri, Jul 1, 2022 at 8:56 PM Ben Cotton <bcotton@xxxxxxxxxx> wrote: > > https://fedoraproject.org/wiki/Changes/GNUToolchainF37 > > This document represents a proposed Change. As part of the Changes > process, proposals are publicly announced in order to receive > community feedback. This proposal will only be implemented if approved > by the Fedora Engineering Steering Committee. > > > == Summary == > Update the Fedora 37 GNU Toolchain to glibc 2.36, binutils 2.38. Is there a way we could get back to shipping up-to-date binutils? I mean, 2.39 should be released on July 8th and the potential release date is August 6th. Also in the 1st half of the year we used to get new GCC, binutils, and glibc. Now somehow in the last releases binutils is one version older. Is there a reason this change happened? Is it schedule related? It does seem that binutils 2.39 should be able to fit. It's tight, but possible. Cheers, david > > The set of core GNU Toolchain packages for Fedora 37 are as follows: > > * GNU C Compiler 12 (first released in Fedora 36) > ** Associated runtimes for C++ (libstdc++), Go (gccgo), OpenMP (gomp), > Fortran (gfortran), D (phobos), Objective C/C++. > * GNU Binary Utilities 2.38 (expected release in Fedora 37) > * GNU C Library 2.36 (expected release in Fedora 37) > * GNU Debugger 12 (immediately available in Fedora 35, 36, and 37) > > The glibc 2.36 change will be tracked in this top-level GNU Toolchain > system-wide update. > > The binutils 2.38 change will be tracked in this top-level GNU > Toolchain system-wide update. > > == Owner == > * Name: [[User:codonell|Carlos O'Donell]] > * Email: carlos@xxxxxxxxxx > > > > == Detailed Description == > The GNU Compiler Collection, GNU C Library, GNU Debugger, and GNU > Binary Utilities make up the core part of the GNU Toolchain and it is > useful for our users to transition these components as a complete > implementation when making a new release of Fedora. > > The GNU C Library version 2.36 is expected to be released in the > beginning of August 2022; we have started closely tracking the glibc > 2.36 development code in Fedora Rawhide and are addressing any issues > as they arise. Given the present schedule Fedora 37 will branch after > the release of glibc 2.36. However, the mass rebuild schedule means > Fedora 37 will mass rebuild (if required) before the final release of > glibc 2.36, but after the ABI is frozen. > > The GNU Binutils version 2.38 was released in February 2022; and we > have already been using this version of binutils in Fedora Rawhide > successfully to build the distribution. Given the present schedule for > Fedora 37 we will continue to use Binutils 2.38 for Fedora 37. > > > == Benefit to Fedora == > Stays up to date with latest features, improvements, security and bug > fixes from gcc, glibc, binutils, and gdb upstream. > > The goal is to track and transition to the latest components of the > GNU Toolchain. > > == Scope == > * Proposal owners: Fedora Toolchain Team (gcc, glibc, binutils, gdb, > ...) developers need to ensure that gcc, glibc, binutils, and gdb in > rawhide are stable and ready for the Fedora 37 branch. > > * Other developers: Given that glibc is backwards compatible and we > have been testing the new glibc in rawhide it should make very little > impact when updated, except for the occasional deprecation warnings > and removal of legacy interfaces from public header files. > > * Release engineering: A mass rebuild is strongly encouraged; > [https://pagure.io/releng/issue/10865 #10865] > > * Policies and guidelines: N/A (not needed for this Change) > * Trademark approval: N/A (not needed for this Change) > * Alignment with Objectives: N/A > > > == Upgrade/compatibility impact == > Any source level changes required for glibc 2.36 will be noted here: > https://sourceware.org/glibc/wiki/Release/2.36#Packaging_Changes > > == How To Test == > The GNU Compiler Collection has its own testsuite which is run during > the package build and examined by the gcc developers before being > uploaded. > > The GNU C Library has its own testsuite which is run during the > package build and examined by the glibc developers before being > uploaded. This test suite has over 6200 tests that run to verify the > correct operation of the library. In the future we may also run the > microbenchmark to look for performance regressions. > > The GNU Binutils has its own testsuite which is run during the package > build and examined by binutils developers before being uploaded. The > regression testsuite is run to verify the correct operation of the > static linker and attendant utilities. > > The GNU Debugger has its own testsuite which is run during the package > build and examined by gdb developers before being uploaded. The > regression testsuite is run to verify the correct operation of the > debugger. > > > == User Experience == > > > == Dependencies == > All packages do not need to be rebuilt due to backwards compatibility. > However, it is advantageous if a mass rebuild is performed during the > Fedora 37 cycle. The mass rebuild would ensure all packages can be > built with the newer compiler and core runtime. > > == Contingency Plan == > > * Contingency mechanism glibc: If glibc 2.36 proves too disruptive to > compiling the distribution we could revert to 2.35, but given that > Rawhide has started tracking glibc 2.36, no show-stopper problems are > expected. At this point we can still revert to upstream version 2.35 > if insurmountable problems appear, but to do so may require a mass > rebuild to remove new symbols from the ABI/API. > > * Contingency mechanism binutils: If binutils 2.38 proves too > distruptive to assembling and linking the distribution we could revert > to 2.37, but given that Rawhide is using 2.38, no show-stopper > problems are expected. At this point we can still revert if > insurmountable problems appear, but to do so may require a mass > rebuild if the defects involve generated binaries. > > * Contingency deadline: Fedora mass rebuild on 2022-07-20. > * Blocks release? > ** Yes, upgrading to glibc 2.36 does block the release. > > > == Documentation == > The gcc manual contains the documentation for the release and doesn't > need any more additional work. > > The binutils manual contains the documentation for the release and > doesn't need any more additional work. > > The glibc manual contains the documentation for the release and > doesn't need any more additional work. > > The gdb manual contains the documentation for the release and doesn't > need any more additional work. > > > == Release Notes == > The GNU C Library version 2.36 will be released at the beginning of > August 2022. The current NEWS notes can be seen here as they are > added: https://sourceware.org/git/?p=glibc.git;a=blob;f=NEWS;hb=HEAD > > The GNU Binary Utilities version 2.38 was released February 2022. The > current release notes can be seen here: > https://sourceware.org/pipermail/binutils/2022-February/119721.html > > > > -- > Ben Cotton > He / Him / His > Fedora Program Manager > Red Hat > TZ=America/Indiana/Indianapolis > _______________________________________________ > devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx > Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx > Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
