I'm trying to reproduce it to see what should be fixed, but I'm not sure I will have time to commit anything until the evening/night (CET). I hope you don't mind waiting. Sorry for any inconvenience.
Karl 2013/4/2 Sebastian Rose <[email protected]>: > libffado-9999-r1, correct. build.log and sandbox.log are attached. > > > On 02/04/13 12:51, Karl Lindén wrote: >> >> I assume your trying to emerge version 9999-r1. Am I right? >> >> The new patch should only apply to the *-r1 ebuils, everything was >> deliberately kept unchanged in the latest commit. In which phase does >> the violation occur? Can you supply more information, like the build >> log? >> >> Regards, >> Karl >> >> 2013/4/2 Sebastian Rose <[email protected]>: >>> >>> The new libffado ebuild generates sandbox violations on my machine. It >>> didn't happen with -9999, something I'm missing? >>> >>> (null)*(null) --------- ACCESS VIOLATION SUMMARY ---------- >>> (null)*(null) LOG FILE: "/var/log/sandbox/sandbox-12357.log" >>> (null)*(null) >>> VERSION 1.0 >>> FORMAT: F - Function called >>> FORMAT: S - Access Status >>> FORMAT: P - Path as passed to function >>> FORMAT: A - Absolute Path (not canonical) >>> FORMAT: R - Canonical Path >>> FORMAT: C - Command Line >>> >>> F: open_wr >>> S: deny >>> P: /dev/snd/controlC0 >>> A: /dev/snd/controlC0 >>> R: /dev/snd/controlC0 >>> C: jackd --version >>> >>> F: open_wr >>> S: deny >>> P: /dev/snd/controlC0 >>> A: /dev/snd/controlC0 >>> R: /dev/snd/controlC0 >>> C: jackd --version >>> (null)*(null) ------------------------------------------- >>> >>> >>> On 01/04/13 14:39, [email protected] wrote: >>>> >>>> >>>> Revision: 2637 Author: lilrc Date: 2013-04-01 14:39:47 +0200 >>>> (Mon, 01 Apr 2013) Log Message: ----------- media-libs/libffado: >>>> Patch to prevent jackd --version being called. Move to EAPI 5 and >>>> base and python-single-r1 eclasses. Specify udev rules directory. Do >>>> python optimizations before merging. > >
