I am getting sandbox access violations when trying to emerge the ebuild. The following is the output at the terminal. ---- An Example Section from the Build Output ---- chmod 0755 /var/tmp/portage/octave-2.0.17/image/usr/libexec/octave/site/exec/i686-pc-linux-gnu mkdir /usr/share/octave ACCESS DENIED mkdir: /usr/share/octave mkdir: cannot create directory `/usr/share/octave': Permission denied chmod 0755 /usr/share/octave --------------------------------------------------- ---- The Output At the End of "ebuild octave-2.0.17.ebuild install" ---- !!! ERROR: app-sci/octave-2.0.17 failed. !!! Function src_install, Line 6, Exitcode 2 !!! make install failed --------------------------- ACCESS VIOLATION SUMMARY --------------------------- LOG FILE = "/tmp/sandbox-octave-2.0.17-7552.log" mkdir: /usr/share/octave mkdir: /usr/share/octave/2.0.17 mkdir: /usr/share/octave/2.0.17/m mkdir: /usr/share/octave mkdir: /usr/share/octave/2.0.17 mkdir: /usr/share/octave/2.0.17/site mkdir: /usr/share/octave/2.0.17/site/m mkdir: /usr/share/octave mkdir: /usr/share/octave/site mkdir: /usr/share/octave/site/m --------------------------------------------------------------------------------
Hi Andrew. Thank you for the report. I have unmasked the 2.0.17-r1 ebuild, - it has this issue fixed. Could you please test how it works now? BTW, what is your arch/profile? George
Yeah, r1 worked great. I'm running a AMD XP... the lines from my make.conf are, CHOST="i686-pc-linux-gnu" CFLAGS="-march=i586 -O3 -pipe" Is this what you were asking for (not entirely sure what you meant by profile)?
