The libstdc++ soname number will be bumped up probably. Then that would fix c++ ABI breakage conflicts till the steam runtime and game updates their c++.
But that will not solve the breakage due to internal gcc libs like libgcc.
A proper fix is static linking of libstdc++/libgcc and co in valve apps and games (it's 2 options on gcc command line...)
what? There is C++11 ABI way before GCC 5. I dont get the issue.
@cjwijtmans It wasn't default in GCC < 5.
Also, so much has changed in GCC 5.x that I'd consider the fact that the soname number hasn't been bumped to be a bug in GCC. Even if most distros are still on 4.x, I strongly recommend Valve take steps to ensure Steam works with 5.x now, before it becomes the standard and breaks every binary package that ever existed for Linux.
c++ is insane and a pain: nothing new here.
Valve should let the games package their c++ runtime (static
linking... to avoid conflict) if they use it.
On 10/4/15, lavacano201014 [email protected] wrote:
@cjwijtmans It wasn't default in GCC < 5.
Also, so much has changed in GCC 5.x that I'd consider the fact that the
soname number hasn't been bumped to be a bug in
GCC. Even if most distros are still
on 4.x, I strongly recommend Valve take steps to ensure Steam works with 5.x
now, before it becomes the standard and breaks every binary package that
ever existed for Linux.
Reply to this email directly or view it on GitHub:
https://github.com/ValveSoftware/steam-for-linux/issues/3825#issuecomment-145287413
Please see this SteamOS community post as reference.