When PHP has been built with the shared-memory session storage engine, it creates a file similar to session_mm_cli0.sem on startup. This results in a sandbox violation when building dev-php5/php-gtk 2.0.0-alpha. Reproducible: Always Steps to Reproduce: 1. Emerge PHP with the sharedmem USE flag. This enables the shared-memory session storage engine. 2. Attempt to emerge php-gtk 2.0.0-alpha Actual Results: --------------------------- ACCESS VIOLATION SUMMARY --------------------------- LOG FILE = "/var/log/sandbox/sandbox-dev-php5_-_php-gtk-2.0.0_alpha-11228.log" unlink: /session_mm_cli0.sem open_wr: /session_mm_cli0.sem unlink: /session_mm_cli0.sem -------------------------------------------------------------------------------- Expected Results: >>> dev-php5/php-gtk-2.0.0_alpha merged. I fix this by: andrewm@ds38-3 /usr/portage/dev-php5/php-gtk $ diff php-gtk-2.0.0_alpha.ebuild php-gtk-2.0.0_alpha.ebuild.new 68a69,70 > addpredict /session_mm_cli0.sem > andrewm@ds38-3 $ ebuild /usr/portage/dev-php5/php-gtk/php-gtk-2.0.0_alpha.ebuild digest andrewm@ds38-3 $ emerge dev-php5/php-gtk
Thanks for reporting, will look into this ASAP.
Ahh yeah, php-gtk doesn't use the php-ext-eclasses src_compile/install methods, thus this still affects it, to solve it just add addpredict /session_mm_cli0.sem, as the bugreporter already did, that's the correct fix. Just FYI, this only happens when you compiled PHP with sharedmem USE flag (it has to do with the mm storage of the sessions module). Best regards, CHTEKK.
Thanks, fixed in CVS.