There's Now More Than 1,100 Games On Steam For Linux

[Xaero_Vincent]

steam-runtime bundles gcc? are you sure? I thought it bundles only those libs you mention above and those conflict with your local gcc - if that is newer

I'm not exactly sure what is all bundled but Steam Runtime is essentially a very stripped down version of Ubuntu 12.04 from my understanding.

[Passso]

If GCC 5.x ends up breaking stuff, then sticking to an LTS distro will only prolong things. 16.04 will certainly have GCC 5.x as will any future distros.

Valve tries to make the Steam Runtime a solution but it isn't perfect as we can tell and Valve's official response is this:

If you are running another distrubiton of Linux we will be unable to offer support as these are not officially supported. If you are having trouble running Steam for Linux on another distribution we recommend switching to Ubuntu 12.04 LTS or 12.10 with the Unity, Gnome, or KDE desktop.

https://support.steampowered.com/kb_...1504-QHXN-8366

If some games need gcc X then Valve will ship a version of gcc X with Steam or require an additional package like all software maintainer do... I really see no problem with that.

I bet they forgot to update their article as 95% of their 12.04 users already switched to 14.04 or more, and Steam keeps working well for them

[tomtomme]

The Steam Runtime has those libraries but the problem is that they conflict.

On Archlinux, I frequently need to run this command to delete certain files from the Steam Runtime, just for Steam to launch with proper 3D accelerated direct rendering:

find ~/.steam/root/ \( -name "libgcc_s.so*" -o -name "libstdc++.so*" -o -name "libxcb.so*" \) -print -delete

I've also had to do this with some older games outside of Steam as well, for instance the very old binary version of Quake 4 Demo included an old libstdc++ library and the game crashes with a segmentation fault until I delete that and use the GCC 4.x system-wide version.

steam-runtime bundles gcc? are you sure? I thought it bundles only those libs you mention above and those conflict with your local gcc - if that is newer

[Xaero_Vincent]

I suppose you imagine a future mess, but it is Valve's work to prevent that.
So if you stick to LTS like Ubuntu 14.04 / 16.04 or OpenSuse 13.1 / 14.1 etc. you will probably never see those bugs happening.

If GCC 5.x ends up breaking stuff, then sticking to an LTS distro will only prolong things. 16.04 will certainly have GCC 5.x as will any future distros.

Valve tries to make the Steam Runtime a solution but it isn't perfect as we can tell and Valve's official response is this:

If you are running another distrubiton of Linux we will be unable to offer support as these are not officially supported. If you are having trouble running Steam for Linux on another distribution we recommend switching to Ubuntu 12.04 LTS or 12.10 with the Unity, Gnome, or KDE desktop.

https://support.steampowered.com/kb_article.php?ref=1504-QHXN-8366

[Passso]

So how many games will stop working on distros shipping GCC 5.1 with the new liibstdc++ ABI enabled and all core components linking to this compiled with the new ABI? Especially considering you have to delete the libstdc++ from the Steam Runtime on many modern distros because it conflicts with the system-wide installed one. I've read that Fedora 23 and Ubuntu 15.10 plan to recompile all their C++-based packages or even all their packages with GCC 5.1 with the new ABI enabled, if applicable.

If problems do occur, I cannot imagine that all or even many of these Steam game developers will try recompiling their games to work with GCC 5.1 because that would break compatability with the older distros used as a minimum requirement for games. I'm hoping things just continue to magically work but I'm not so sure, seeing the conflicts that already exist with the Steam Runtime libs in modern distros.

Could Docker be a solution here?

Perhaps run Debian Wheezy-based SteamOS inside a Docker container on-top of a GCC 5.1 enabled distros?

https://registry.hub.docker.com/u/tianon/steamos/
https://maci0.wordpress.com/2014/05/...am-pidgin-vlc/

I suppose you imagine a future mess, but it is Valve's work to prevent that.
So if you stick to LTS like Ubuntu 14.04 / 16.04 or OpenSuse 13.1 / 14.1 etc. you will probably never see those bugs happening.

[Xaero_Vincent]

So how many games will stop working on distros shipping GCC 5.1 with the new liibstdc++ ABI enabled and all core components linking to this compiled with the new ABI? Especially considering you have to delete the libstdc++ from the Steam Runtime on many modern distros because it conflicts with the system-wide installed one. I've read that Fedora 23 and Ubuntu 15.10 plan to recompile all their C++-based packages or even all their packages with GCC 5.1 with the new ABI enabled, if applicable.

If problems do occur, I cannot imagine that all or even many of these Steam game developers will try recompiling their games to work with GCC 5.1 because that would break compatability with the older distros used as a minimum requirement for games. I'm hoping things just continue to magically work but I'm not so sure, seeing the conflicts that already exist with the Steam Runtime libs in modern distros.

Could Docker be a solution here?

Perhaps run Debian Wheezy-based SteamOS inside a Docker container on-top of a GCC 5.1 enabled distros?

https://registry.hub.docker.com/u/tianon/steamos/

https://maci0.wordpress.com/2014/05/...am-pidgin-vlc/

couldn?t steam runtime just add gcc and libstdc++ 4.8 and the stuff thats connected with it?

The Steam Runtime has those libraries but the problem is that they conflict.

On Archlinux, I frequently need to run this command to delete certain files from the Steam Runtime, just for Steam to launch with proper 3D accelerated direct rendering:

find ~/.steam/root/ \( -name "libgcc_s.so*" -o -name "libstdc++.so*" -o -name "libxcb.so*" \) -print -delete

I've also had to do this with some older games outside of Steam as well, for instance the very old binary version of Quake 4 Demo included an old libstdc++ library and the game crashes with a segmentation fault until I delete that and use the GCC 4.x system-wide version.

[tomtomme]

It's a never ending circle. Bad ports mean people don't want to play the linux version. Which means less people using Linux to play the games which lowers the percentage. Ultimately port quality and graphics driver stability are the only thing that will drive adoption. You need both to be as good as or better than Windows.

the main thing that would drive adoption would be a main manufacturer (like Dell?) pre-installing linux / steamOS on cheap but fast and quiet machines. let?s hope valves partners get that right...

[tomtomme]

So how many games will stop working on distros shipping GCC 5.1 with the new liibstdc++ ABI enabled and all core components linking to this compiled with the new ABI? Especially considering you have to delete the libstdc++ from the Steam Runtime on many modern distros because it conflicts with the system-wide installed one. I've read that Fedora 23 and Ubuntu 15.10 plan to recompile all their C++-based packages or even all their packages with GCC 5.1 with the new ABI enabled, if applicable.

If problems do occur, I cannot imagine that all or even many of these Steam game developers will try recompiling their games to work with GCC 5.1 because that would break compatability with the older distros used as a minimum requirement for games. I'm hoping things just continue to magically work but I'm not so sure, seeing the conflicts that already exist with the Steam Runtime libs in modern distros.

Could Docker be a solution here?

Perhaps run Debian Wheezy-based SteamOS inside a Docker container on-top of a GCC 5.1 enabled distros?

https://registry.hub.docker.com/u/tianon/steamos/
https://maci0.wordpress.com/2014/05/...am-pidgin-vlc/

couldn?t steam runtime just add gcc and libstdc++ 4.8 and the stuff thats connected with it?

[Hohlraum]

I do not understand why some of you whine so much about "bad ports". Yes performance may be a little behind but we now have real games and I do not regret any of my games bought on Steam, as they are all working well.

If Steam OS / Linux go beyond 10% there will be really less and less bugs/performance issue and more true native games.

Btw the fact is that now the "triple" Win/Mac/Lin version is frequent, this is very encouraging.

It's a never ending circle. Bad ports mean people don't want to play the linux version. Which means less people using Linux to play the games which lowers the percentage. Ultimately port quality and graphics driver stability are the only thing that will drive adoption. You need both to be as good as or better than Windows.

[Xaero_Vincent]

So how many games will stop working on distros shipping GCC 5.1 with the new liibstdc++ ABI enabled and all core components linking to this compiled with the new ABI? Especially considering you have to delete the libstdc++ from the Steam Runtime on many modern distros because it conflicts with the system-wide installed one. I've read that Fedora 23 and Ubuntu 15.10 plan to recompile all their C++-based packages or even all their packages with GCC 5.1 with the new ABI enabled, if applicable.

If problems do occur, I cannot imagine that all or even many of these Steam game developers will try recompiling their games to work with GCC 5.1 because that would break compatability with the older distros used as a minimum requirement for games. I'm hoping things just continue to magically work but I'm not so sure, seeing the conflicts that already exist with the Steam Runtime libs in modern distros.

Could Docker be a solution here?

Perhaps run Debian Wheezy-based SteamOS inside a Docker container on-top of a GCC 5.1 enabled distros?

https://registry.hub.docker.com/u/tianon/steamos/
https://maci0.wordpress.com/2014/05/...am-pidgin-vlc/