On Tue, Jul 25, 2023 at 11:44 AM Florian Weimer <fweimer@xxxxxxxxxx> wrote: > > * Josh Boyer: > > > On Tue, Jul 25, 2023 at 10:53 AM Miro Hrončok <mhroncok@xxxxxxxxxx> wrote: > >> > >> On 25. 07. 23 16:42, Florian Weimer wrote: > >> > * Miro Hrončok: > >> > > >> >> glibc32 codonell, fweimer, jakub, mcermak > >> > > >> > Is this about FTBFS issues? There isn't any recent build failure in > >> > Koji, so I don't get why it's on this list? > >> > >> The build currently in Rawhide was done on Fedora 36 which is end of life. > >> > >> Apparently the release engineering team has not rebuilt this package in a mass > >> rebuild at least since Fedora 35. > >> > >> To remove it from the list, build the package on Rawhide please. > > > > Or we could not, and drop i686 completely. > > If we drop glibc32, we can't build any 32-bit code at all because GCC > will no longer support -m32. In this regardm x86-64 is different than > the other Fedora architectures which can target bare metal 32-bit even > from 64-bit-only compilers. > > Are bootloaders fully treated as firmware and no longer built by Fedora? > At least the shim package does not come with corresponding source code > AFAICS. But I expect that there are other 32-bit pre-boot packages that > we still rebuild. > > We need to fix this GCC build issue for CentOS 10 eventually, and at > that point, we won't need glibc32 anymore. It's been a constant source > of annoyance. Necessity is the mother of all invention. If you need this solved by CentOS Stream 10, you really want to solve it now and get that solution into F39 or F40 at the latest. josh _______________________________________________ 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, report it: https://pagure.io/fedora-infrastructure/new_issue