Torcs' configure script links initial testing programs with openal, and runs them starting with the plib version check. However, on (apparently) some platforms, linking with openal causes the program to open some files in /dev/snd for writing upon start. This doesn't work well with the sandbox (segmentation fault in my case).
On my platform, setting SANDBOX_WRITE to "/dev/snd" before emerging torcs fixed the issue. I suggest adding something of the sort to the ebuild.
Steps to Reproduce:
please reopen with the output from emerge --info and the full output from the attempt at emerging.
Sufficient information is provided at the URL I included previously.
please provide the requested information attached to this bug. Thanks.
The requested information is irrelevant to this bug, and doesn't show the problem. Compiling an empty C program with -lopenal and running it using strace will show whether it tries to write to /dev/snd/ files. If it does, it is a sandbox violation during the configure phase of the build.
You're difficult to help.
I know... I am just not sufficiently motivated to run useless builds and produce useless output after I found a workaround myself and told you how to fix the problem. For all I care, this ebuild can remain broken. :)