Created attachment 523962 [details] emerge--info--dev-java/oracle-jdk-bin-1.8.0.162-r1 While emerging dev-java/oracle-jdk-bin-1.8.0.162 and the verion befor (161) it break a access violation, like: --- * --------------------------- ACCESS VIOLATION SUMMARY --------------------------- * LOG FILE: "/var/log/sandbox/sandbox-16284.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: mkdir S: deny P: /tmp/hsperfdata_portage A: /tmp/hsperfdata_portage R: /tmp/hsperfdata_portage C: /opt/oracle-jdk-bin-1.8.0.162/bin/java -version * ------------------------------------------------------------------------ !!! When you file a bug report, please include the following information: GENTOO_VM=oracle-jdk-bin-1.8 CLASSPATH="" JAVA_HOME="/opt/oracle-jdk-bin-1.8.0.162" JAVACFLAGS="-source 1.6 -target 1.6" COMPILER="" and of course, the output of emerge --info =mariadb-10.1.31 --- I could fully emerge the jdk by doing a simple # mkdir -p /tmp/hsperfdata_portage && chmod 777 /tmp/hsperfdata_portage which was fine, but I have a tmpfs /temp and now, emerging mariadb with USE jdbc, I get hit with the same. ? Do you want me to also attach: emerge --info =mariadb-10.1.31 Though I guess it is a pure oracacle-jdk-bin issue
Please attach the entire build log to this bug report.
Have you modified /etc/sandbox.conf? It normally includes this: # Tempory storage SANDBOX_WRITE="/tmp/:/var/tmp/"
@James, very thanks! My /etc/sandbox.conf shows: SANDBOX_WRITE="/tmp/portage/:/var/tmp/" Feel free to close this bug! My fault: Because I do the emerge in "/tmp/portage", I "short circuited" and changed /tmp to the directory I do emerge :( By the way, what this is showing: - most of portage ebuilds do not use "/tmp" - dev-java/oracle-jdk-bin directory "/tmp/hsperfdata_portage" remembers me of ancient times with another operating system ("hsperfdata")
(In reply to Ulenrich from comment #3) > Feel free to close this bug! My fault: Because I do the emerge in > "/tmp/portage", I "short circuited" and changed /tmp to the directory I do > emerge :( No problem. > By the way, what this is showing: > - most of portage ebuilds do not use "/tmp" > - dev-java/oracle-jdk-bin directory "/tmp/hsperfdata_portage" > remembers me of ancient times with another operating system ("hsperfdata") I don't know why it picks this path but there's not much we can do about it.
