Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 307635

Summary: torcs-1.3.1 configure script links programs with openal, which makes problems with sandbox
Product: Gentoo Linux Reporter: Faustus <orlovm>
Component: [OLD] GamesAssignee: Gentoo Games <games>
Status: RESOLVED CANTFIX    
Severity: normal    
Priority: High    
Version: unspecified   
Hardware: All   
OS: Linux   
URL: http://forums.gentoo.org/viewtopic-p-6192629.html
Whiteboard:
Package list:
Runtime testing required: ---

Description Faustus 2010-03-03 16:21:51 UTC
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.

Reproducible: Always

Steps to Reproduce:
Comment 1 Mr. Bones. (RETIRED) gentoo-dev 2010-03-04 17:18:28 UTC
please reopen with the output from emerge --info and the full output from the attempt at emerging.
Comment 2 Faustus 2010-03-04 17:23:07 UTC
Sufficient information is provided at the URL I included previously.
http://forums.gentoo.org/viewtopic-p-6192629.html
Comment 3 Mr. Bones. (RETIRED) gentoo-dev 2010-03-04 17:25:31 UTC
please provide the requested information attached to this bug.  Thanks.
Comment 4 Faustus 2010-03-04 18:51:57 UTC
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.
Comment 5 Mr. Bones. (RETIRED) gentoo-dev 2010-03-04 18:53:23 UTC
You're difficult to help.
Comment 6 Faustus 2010-03-04 18:57:34 UTC
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. :)