On 2025-12-22 21:12, Siddhesh Poyarekar wrote:
FYI, we have gcc 16 built in a side tag for testing, in preparation for
a rebase in F44 by the Toolchain Update checkpoint[1]. I'm running
scratch build tests[2][3] for various packages (some of you must have
seen bugs coming your way already) in preparation for the rebase, but if
any of you want to get ahead of the line and verify your own packages,
you may do so by doing a scratch build against f44-build-side-124978.
Just to loop back on this, I'm maintaining a CSV, attempting to classify
the failures I've found over the course of the mass prebuild:
https://github.com/siddhesh/mass-prebuild-logs/blob/main/gcc16-prebuild-report.out
The containing project has some scripts I've hacked together to classify
the failures, in case there's interest in seeing them; I typically do a
./download-logs.sh followed by ./process-logs.sh. The failures of
interest to packagers would be classified as PKGBUG:.*, although
Inspect:.* are also interesting since they're the once I haven't managed
to get to yet.
I know I had promised to file bugs but I'm afraid I haven't found enough
time to do that, hence sharing this list here. As a reminder, the mass
prebuild copr is here:
https://copr.fedorainfracloud.org/coprs/siddhesh/mbp-gcc-16/
Thanks,
Sid
--
_______________________________________________
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
