I personally use Debian Sid more than 12 years, but for my fellows I do packages for stable releases.
I have build chroots for both channels (releases), there's no issue to build something. I thought it was done by someone already and relevant experience exists but isn't common to do it on regular basis. SY, Konstantin Demin чт, 20 нояб. 2025 г., 01:00 Micha Lenk <[email protected]>: > Hello Konstantin, > > Am 19. November 2025 15:26:26 MEZ schrieb Konstantin Demin < > [email protected]>: > >I'm curious how do DDs/DMs do backporting of fresh GCC toolchains on > >stable releases. > > > >Notes: I'm currently working on merge requests for mingw-w64, and > >gcc-mingw-w64 was recently rebased on top of gcc 15, so I'd need to > >get gcc 15 working on Debian 13 Trixie to continue local research and > >tests. I've tried once to backport GCC 15 on my own but the resulting > >dependencies are somewhat broken (e.g. libcc1 for gcc itself). > >Backporting binutils was a quite simple task but not gcc. > > > >PS: I can perform tests on Debian Sid, but for some reasons I need to > >do this on Trixie too. > > I believe doing such things can have good reasons, and it is always a good > idea to share results with others who could be interested. > > Yet Debian backports exists mostly to provide newer versions (than > available in stable) of binaries, but built in the same build environment > as stable. And GCC definitely counts as "build environment" in my books. > The importance of building in the same build environment as stable is > founded on the experience that even subtle changes in the tool chain can > cause incompatibilities between libraries and binaries, which would defeat > the purpose of having backports in the first place. > > For this reason, sorry, no, we can't have any GCC in Debian backports. > However, I wouldn't wonder if GCC backports already exist elsewhere. > > Other idea: Did you already consider running your mingw-w64 merge request > work within a chroot environment? That way you could run GCC in a sid > environment without having to update your entire system to sid as well. > This would possibly even save you having to rebuild GCC (and its > dependencies) yourself... > > Kind regards, > Micha > >
