Created attachment 602306 [details] build.log > -- Configuring done > -- Generating done > -- Build files have been written to: /var/tmp/portage/net-libs/webkit-gtk-2.26.2/work/webkit-gtk-2.26.2_build > >>> Source configured. > * --------------------------- ACCESS VIOLATION SUMMARY --------------------------- > * LOG FILE: "/var/log/sandbox/sandbox-4.log" > * > 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: utimes > S: deny > P: /var/cache/ccache > A: /var/cache/ccache > R: /var/cache/ccache > C: ccache /usr/bin/x86_64-pc-linux-gnu-g++ -DQT_NO_CAST_TO_ASCII -DQT_NO_EXCEPTIONS -DQT_STRICT_ITERATORS -DWITH_APP_BUN > DLE -Isrc/zxcvbn_autogen/include -I/var/tmp/portage/app-admin/keepassxc-2.5.1/work/keepassxc-2.5.1/src -Isrc -I/var/tmp/ > portage/app-admin/keepassxc-2.5.1/work/keepassxc-2.5.1/src/zxcvbn -DNDEBUG -O2 -pipe -march=skylake -mtune=skylake -mabm > -mrtm -fno-common -Wall -Wextra -Wundef -Wpointer-arith -Wno-long-long -Wformat=2 -Wmissing-format-attribute -fvisibili > ty=hidden -fvisibility-inlines-hidden -fstack-protector-strong -fno-exceptions -fno-rtti -Wnon-virtual-dtor -Wold-style-cast -Woverloaded-virtual -Werror=format-security -Wcast-align -pie -fPIE -std=c++11 -fsized-deallocation -MD -MT src/CMakeFiles/zxcvbn.dir/zxcvbn_autogen/mocs_compilation.cpp.o -MF src/CMakeFiles/zxcvbn.dir/zxcvbn_autogen/mocs_compilation.cpp.o.d -o src/CMakeFiles/zxcvbn.dir/zxcvbn_autogen/mocs_compilation.cpp.o -c src/zxcvbn_autogen/mocs_compilation.cpp > > [...]
Why are we seeing /var/tmp/portage/app-admin/keepassxc-2.5.1/work/keepassxc-2.5.1/src/zxcvbn/zxcvbn.c stuff in the logs for the problematic ccache calls instead of webkit-gtk stuff?
I don't know for sure but I guess because both packages were emerging at the same time and are showing the same failure (bug 704560).
I don't think there's anything to do here for webkit-gtk or even keepassx, but ccache or portage or something rather?
The failure is that webkit-gtk (like keepassxc) will use ccache when present. Because I never used ccache with portage, ccache's cache folder isn't writable for portage user and folder isn't even allowed in sandbox (FEATURES=ccache would take care of that but like said, I don't use it). But that failure itself isn't the problem. The problem is that webkit-gtk's build system is looking for ccache on host system and will use it when found. This must be disabled.
ccache is installed here, (i was hoping it might save some time with merging chromium). As far as i can tell it was not invoked by net-libs/webkit-gtk-2.26.2, and did not result in a failure to emerge net-libs/webkit-gtk-2.26.2. # eshowkw dev-util/ccache net-libs/webkit-gtk ; ls $(grep -i cache /etc/portage/make.conf | cut -d \" -f2) Keywords for dev-util/ccache: | | u | | a a a p s r | n | | l m r i p h m s p i m | e u s | r | p d a m a p c x p 6 3 a s i | a s l | e | h 6 r 6 6 p 6 8 p 8 9 s r c p | p e o | p | a 4 m 4 4 c 4 6 a k 0 h c v s | i d t | o ---------+-------------------------------+-------+------- 3.7.2 | + + + + + + + + + + + + + ~ ~ | 7 o 0 | gentoo [I]3.7.4 | + + + + + + + + + ~ + ~ + ~ ~ | 7 o | gentoo 3.7.5 | ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ | 7 # | gentoo 3.7.6 | ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ | 7 o | gentoo Keywords for net-libs/webkit-gtk: | | u | | a a a p s r | n | | l m r i p h m s p i m | e u s | r | p d a m a p c x p 6 3 a s i | a s l | e | h 6 r 6 6 p 6 8 p 8 9 s r c p | p e o | p | a 4 m 4 4 c 4 6 a k 0 h c v s | i d t | o ----------+-------------------------------+----------+------- 2.24.4 | ~ + ~ + ~ ~ ~ + o o o o ~ o o | 6 o 4/37 | gentoo [I]2.26.2 | o + o o o o o o o o o o o o o | 6 o | gentoo 0 1 2 3 4 5 6 7 8 9 a b c ccache.conf d e f lost+found www-client
webkit-gtk build system doesn't do anything with ccache - it only does so with the Mac port, but we are building the GTK port.
This is a portage bug (bug 704848): Like said in comment #2, I was building net-libs/webkit-gtk and app-admin/keepassxc at the same time (during `emerge --jobs 2 --load-average 5.95 --update world`). It was keepassxc which caused the sandbox violation (see bug 704560). However, this caused net-libs/webkit-gtk to fail with the same sandbox violation because SANDBOX_LOG is currently being shared. Closing this one as invalid because there's nothing left to do for net-libs/webkit-gtk.
