Some of my experiences (and issues found) trying to get this working on Arch Linux x86_64...
As I stated in a previous post, most of the library dependencies are no problem at all. The lib32 versions of nearly everything are available in the standard repos or AUR, though it is a bit of a pain figuring out what they all are using ldd. One of these days I'll probably to a PKGBUILD to automatically get all of 'em. The only libraries that ARE a problem are Allegro and Dumb. Arch has moved on to Allegro 4.4, and AGS still expect 4.2. However, the copies included with AGS312 seem to work fine, mostly. More on that in a sec. Dumb (specifically libdumb.so and libaldmb.so) are another issue. The Dumb maintainers suggest building Dumb as a static library, and the Arch folks appear to follow that advice. As such there is no .so library to link to. As I stated before, the versions of these libs from Ubuntu appear to work with no trouble. (Perhaps later I shall try to build them for Arch myself.)
Onto the odd issues. I tried both Ags 3.1.2 SP1 and 2.72 RC2, as well as EvilTypeGuy's builds of 2.72 and 2.62 (just 'cause). So far all of these tests are just with a few minutes of 5 Days a Stranger, so I'm not sure how universal they are. 2.72 RC2 appears to work flawlessly. There is no fading screen, but otherwise no problem. 3.1.2 SP1 works fine in fullscreen, except for the known fading issue. I had trouble with it windowed. The intro of the game worked, but as soon as I clicked the 'start' button the program exited with a segfault. The actual error message:
Shutting down Allegro due to signal #11
Any ideas?
The patched version of 3.1.2 would not even start. It gave me this error message:
symbol lookup error: /opt/lib32/usr/lib/liballeg.so.4.2: undefined symbol: _blender_trans24
This is using the copy of liballeg.so.4.2 that is packaged with the AGS runtime. Both of ETG's builds I tried gave the exact same error message. Could this be clue to the origin of the fading bug?
A quick glance around teh internets suggests these two errors may be related, and that they probably have to do with how Allegro was linked. It may simply be incompatibility with Allegro and my system libs, but I don't know how to tell for sure.
Anyway, that's how it's working so far. Will update with any other interesting tidbits.
HoN
As I stated in a previous post, most of the library dependencies are no problem at all. The lib32 versions of nearly everything are available in the standard repos or AUR, though it is a bit of a pain figuring out what they all are using ldd. One of these days I'll probably to a PKGBUILD to automatically get all of 'em. The only libraries that ARE a problem are Allegro and Dumb. Arch has moved on to Allegro 4.4, and AGS still expect 4.2. However, the copies included with AGS312 seem to work fine, mostly. More on that in a sec. Dumb (specifically libdumb.so and libaldmb.so) are another issue. The Dumb maintainers suggest building Dumb as a static library, and the Arch folks appear to follow that advice. As such there is no .so library to link to. As I stated before, the versions of these libs from Ubuntu appear to work with no trouble. (Perhaps later I shall try to build them for Arch myself.)
Onto the odd issues. I tried both Ags 3.1.2 SP1 and 2.72 RC2, as well as EvilTypeGuy's builds of 2.72 and 2.62 (just 'cause). So far all of these tests are just with a few minutes of 5 Days a Stranger, so I'm not sure how universal they are. 2.72 RC2 appears to work flawlessly. There is no fading screen, but otherwise no problem. 3.1.2 SP1 works fine in fullscreen, except for the known fading issue. I had trouble with it windowed. The intro of the game worked, but as soon as I clicked the 'start' button the program exited with a segfault. The actual error message:
Shutting down Allegro due to signal #11
Any ideas?
The patched version of 3.1.2 would not even start. It gave me this error message:
symbol lookup error: /opt/lib32/usr/lib/liballeg.so.4.2: undefined symbol: _blender_trans24
This is using the copy of liballeg.so.4.2 that is packaged with the AGS runtime. Both of ETG's builds I tried gave the exact same error message. Could this be clue to the origin of the fading bug?
A quick glance around teh internets suggests these two errors may be related, and that they probably have to do with how Allegro was linked. It may simply be incompatibility with Allegro and my system libs, but I don't know how to tell for sure.

Anyway, that's how it's working so far. Will update with any other interesting tidbits.
HoN