On Tuesday, February 18, 2025 7:15:34 PM Eastern Standard Time Justin Zobel wrote: > On 19/2/25 10:26, Joshua Goins wrote: > > Someone noticed a build failure on some systems (NixOS and Slackware it > > seems) due to C++ funkiness. They fixed it, and I cherry-picked it to > > 6.3. Can we get a respin or a 6.3.1.1? Thanks! > > If it only affects two distros, I think having them carrying the patch > downstream is more suitable than re-spinning (something in my opinion we > should never do) or creating a new tarball, e.g. 6.3.1.1.
I thought about this, but the fact that it's not compilable is kinda bad for something like plasma-desktop (it also reflects badly on KDE if someone has to patch our newly released software to make it work.) As of writing, the extra release happened anyway. > What is different about these two distros that only they were affected? > Perhaps it is something we can add tests or CI jobs for. This would be good IMO, I'm worried that something like this slipped past us. I'm still not certain what compilers trigger this, the commit message says GCC14. So maybe we need a more recent GCC and/or clang? tangent: really wish this kind of stuff would stop happening in C++. why is it that some code can compile and link fine in one setup, and then completely break in another? 🙂 I *know* the reason, it's just frustrating. Josh
