Linux build process not working as expected about zquestclassic HOT 5 CLOSED

How did you compile Allegro? (You may have to tinker with the configuration to enable sound support? You can try asking at the Allegro forums.) Does sound work in any application using that build of Allegro?

from zquestclassic.

You can also try compiling the various sound libraries from source (in the other/ directory) rather than using the provided binaries.

Sorry I can't help more; the only Linux machine I use has never been able to get sound to work with ZC. The developer who compiled the 2.50.2 binaries is no longer actively involved with development, and the rest of us use Windows.

from zquestclassic.

That's unfortunate. To clarify, I didn't compile allegro, I just let ZC use the pre-compiled library from the git repo. I can try building it and make another attempt.

from zquestclassic.

So I looked at it over the weekend. I did succeed in building allegro with alsa, but I ended up figuring out that I don't actually need alsa for the audio to work.

It turned my sound problem stemmed from the fact that I was depending on it to pipe audio through pulseaudio, which, without alsa, is not what is done. Sound does work if I run it from my main desktop user account, which, from what I gather, means it has to be run from an account with direct access to the sound device. So it shouldn't be a problem in most cases.

Everything but midi music is working, which I investigated and I'll add a different issue for.

I have added a pull request with a fix for alunixac.h

from zquestclassic.

Should this fix have been merged into the 2.55 branch (default)? It's failing for me too without it.
EDIT Manually patching it in doesn't fix it; in fact alunixac.h isn't even generated...

from zquestclassic.