Re: gcc: update to 12.2.0.

[TeusLollo <TeusLollo@users.noreply.github.com>]

[-- Attachment #1: Type: text/plain, Size: 1778 bytes --]

New comment by TeusLollo on void-packages repository

https://github.com/void-linux/void-packages/pull/34902#issuecomment-1257064352

Comment:
> I apologise for coming off strongly, I never intended to

I myself should apologize for the walls of text, and maybe the excessively rough tone of my answers (However, this text-based medium is that it is, and when being read it always sounds rough, in my experience)

But point still stands, and I believe it's not just personal, glibc 2.36 did changes that were justified, and we should upgrade, since otherwise, being stuck on glibc 2.35 while gcc moves forward, is likely to cause myriads of other problems and headaches in the future (With potentially no end in sight, since we don't know if/when EAC will finally be updated properly), as well as depriving all users, for all applications and tooling, of numerous security and performance benefits (Which glibc 2.36 has, notably so, especially compared to recent releases). 

All of this would be so simple if EAC were to be finally updated after almost 2 months, if the Steam-client could finally be recompiled to 64-bit x86_64 and packaged into an AppImage (That would solve most problems Flatpak currently has, I personally think), or if otherwise coding practices were just a tiny bit better, and not "barely functional". 

But hey, even Nvidia recently dropped an open-source driver. If that could happen, maybe EAC and Steam could finally put their stuff together? One can hope.

Anyway, personally I believe a shim to do a sort of translate-call at Proton level will probably be what happens, since even Ubuntu and its derivatives are eventually going to meet this problem if EAC is not fixed timely, and I doubt they will stick to glibc 2.35 just for that.