Hello,
TL;DR; I'm happy to announce that we're now building snapshots of
upstream gcc trunk into a `rawhide-gcc-snapshot`[1] target in koji and
in copr[2] for packagers to test their code with the bleeding edge
compiler and fix issues early, potentially making mass rebuilds
following toolchain rebases smoother.
========================================================================
Several package maintainers expressed interest in easier access to a gcc
toolchain build that they could use to test their code in CI and shift
left the pain of the rebase we do in rawhide at the end of every
calendar year. Additionally, the new milestone for toolchain rebases in
the Fedora release process, combined with the mass rebuild milestone
continually creeping closer to the beginning of the year made it quite
hard for us to push out a stable enough compiler in time, forcing us to
rethink our approach to the rebase process for gcc in rawhide.
Because of this, we started building these snapshots earlier this year
to practice making a test toolchain available for the community to try
things and also to periodically get a view of everything that could
potentially break in a distro due to an upstream compiler change,
allowing us and the Fedora community to adjust sooner and avoid the mad
rush during the mass rebuild.
What you get
============
We're building the latest snapshot off trunk into the
`rawhide-gcc-snapshot` target[1] once roughly every 3 weeks. Alongside
that, we're also building dated snapshot repos in copr[2] in case one
wants to test with a specific past snapshot to, e.g. provide bisect
seeds for an issue.
The toolchain is C, C++ and Fortran only for now, mainly because we know
those will mostly just work. The algol target snuck in there because I
forgot to disable it, I'll be disabling that in the next snapshot :)
Maybe we'll enable more languages in future if we find they're not that
disruptive.
What doesn't work yet
=====================
The latest snapshot built gcc17 (i.e. next year's stable gcc that we've
started development on upstream) and I was able to create a new snapshot
branch and build the corresponding annobin for it in the
rawhide-gcc-snapshot target. I haven't however been able to branch and
build libtool since I don't have maintainer rights for it. I'm hoping
to have that fixed up in the next week or so. I also haven't started
building annobin and libtool into the copr repos yet, so they likely
won't be usable at the moment. I will be doing that in the next week as
well, which is when I'll do the next snapshot.
Reporting issues
================
The Fedora bugzilla is not the right place for reporting issues with
snapshots since they'll be way out of sync with rawhide for much of the
year. If you find issues, you'll need to reduce and report them
upstream[3]. Please note that the snapshots will tend to be quite
volatile at some points during the year because of upstream putting in
features, pulling them out, breaking ABI, etc. I reckon we'll know over
the course of this calendar year exactly how volatile it would be in
practice, but in general I'd recommend for now not using it for any
CI/testing that needs to have a high success rate.
Thanks,
Sid
[1] https://koji.fedoraproject.org/koji/buildtargetinfo?targetID=57105
[2] https://copr.fedorainfracloud.org/groups/g/gcc-team/coprs/
[3] https://gcc.gnu.org/bugzilla/
--
_______________________________________________
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://forge.fedoraproject.org/infra/tickets/issues/new
