It would only move on from complaining about libstdc++.so.6 after I installed lib32stdc++6. On the other hand, I didn't test the i386 build as I only noticed the i386 pattern in maybe the following package or the one after.

==============================================================
➢ Slay the Spire
➢ Update and version tested: 12-13-2020 Linux version
➢ System tested: Linux Mint 21, kernel 5.15.0-50-generic
➢ Small update: The game seems mostly functional, at least up until completing a normal run. The only issues I noticed are that it can't fill the entire screen in borderless window mode, and the default screenshot tool from Linux Mint makes the game minimize.
==============================================================

I just thought about something...

If someone wants to, let's say, "hijack" this thread to report whether a Linux game from GOG works on Steam Deck or not, since it uses a Linux distro by default, I think it would still be on topic.

I can't test games on the Deck myself, as I don't have one, but if someone has and wants to report his/her findings here, feel free to do so!

I don't see how this is that useful. Wouldn't it be better to post in the game's forum instead of searching for a specific game in a giant thread?

Some of the game forums are about as active as my social calendar, others don't exist, and at the end of the day, the general forum is a big target.

I don't agree in this situation. If your goal is to see if someone can answer your question, sure the general forum has more eyes on it. But I don't want to scroll thru a giant thread to see if a game I'm interested in is mentioned. It's so much faster to look at the game's forum.

So if your goal is to let someone know if Game X runs on platform Y I would post it on the game's forum. Though honestly it's no big deal to just try and run it yourself.

Here dies my interest for this thread.

Why would I want to get Linux compatibility report mixed up with advertisement for the handheld console from the biggest DRM provider out there?

First, it isn't a console. From what I was able to gather, it is a full computer with an unlocked BIOS, just with a console-oriented hardware design.
Second, the device uses Linux. A modification of Arch Linux, in fact. And Arch systems aren't covered by system requirements here on GOG, even if they'd be otherwise fully compatible. And the purpose of this thread is to say whether it is compatible or not, and how to achieve compatibility when it is not a simple case of installing it.
Third, due to the unlocked BIOS, people can install the OS they want, in case they'd like something other than SteamOS 3. But then there's still the variable of hardware, which can affect compatibility.
Fourth, lest we forget GOG's own take on the Deck.

It's not a bad idea, but searching the forums is a bit of a pain. So to find a specific game's quirks solutions in this giant thread might be asking too much. To be fair, it's also the case in its current state, but I commend your efforts.

I do fully support including Steam Deck results here, as people still (for some crazy reason, despite GOG's "support") still want to play GOG games on the Steam Deck and the usual place for Steam Deck workarounds is the Steam-specific ProtonDB. So to have a GOG specific place for hints and tips would be useful.

I just wish I had a Steam Deck and that Valve wasn't on my boycott list.

Addendum:
(Tested the 64-bit game in Fedora 37, Xfce edition, with a x86_64 acrchitecture) It may complain about not being able to open the libraries libSDL2-2.0.so.0 and libGLU.so.1. In that case, you need to install, respectively, SDL2 (sudo dnf install SDL2) and mesa-libGLU.x86_64 (sudo dnf install mesa-libGLU.x86_64). Other than that, from some short tests, it seems to run similarly to Darvond's test and my tests in other systems.

==============================================================
➢ Hollow Knight
➢ Update and version tested: 1.5.78.11833, Linux version
➢ System tested: Linux Mint 21.1, kernel Linux 5.15.0-56-generic x86_64
➢ Behavior observed: After ~12 hours of game, it appears to work mostly fine; only issue observed is that connecting the controller after starting the game makes the dash button in the controller not work (RT on the Xbox One controller).
==============================================================

==============================================================
➢ What the Golf?
➢ Update and Version Tested: Squints... Let's just call that Linux 15.
➢ System Tested: Fedora Linux 39, Kernel 6.6.14 and several before.
➢ It's a Unity game, but they actually bothered to optimized it. Still makes my fans spin up, but that's the price of unity. Runs fine, but I wish the par challenges were jettisoned from the game. Controller works too!
==============================================================
➢ Jazz Jackrabbit 2
➢ Update and version tested: Just kidding, I'm using the Jazz 2 Resurrected source port. I've been using it since ...Probably 0.6.0?
➢ Same system tested.
➢ It runs a bit hot at fullscreen, but that's also because I've been driving it above 60 FPS in those cases. No frame drops, and having a native version is pretty damn amazing. It's even partly compatible with Jazz2+, but most of the features there are out of canon for vanilla anyways!
==============================================================
➢ Block'hood
➢ Update/version tested: This game hasn't updated since 2018.
➢ Hold on, gotta wait for this slow installer to finish extracting.
➢ It runs about as well as a 2018 3D Unity game made by someone who was trying to make an artsy game. (At speed, but not quietly.)
➢ Trying to execute it directly doesn't accomplish a whole lot. Use the runner script.
==============================================================