On 2018.11.13 12:11, tu...@posteo.de wrote:
Hi,
I got a weird looking error while upgrading/recompiling nasm:
[snip....]
-- Configuring done
-- Generating done
-- Build files have been written to:
/var/tmp/portage/media-libs/libjpeg-turbo-2.0.1/work/libjpeg-turbo-2.0.1-abi_x86_64.amd64
>>> Source configured.
* --------------------------- ACCESS VIOLATION SUMMARY
---------------------------
* LOG FILE: "/var/log/sandbox/sandbox-16492.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: fopen_wr
S: deny
P: /?
A: /?
R: /?
C: /usr/bin/nasm /?
*
--------------------------------------------------------------------------------
!!! When you file a bug report, please include the following
information:
GENTOO_VM= CLASSPATH="" JAVA_HOME=""
JAVACFLAGS="" COMPILER=""
and of course, the output of emerge --info =libjpeg-turbo-2.0.1
*
* The following package has failed to build, install, or execute
postinst:
*
* (media-libs/libjpeg-turbo-2.0.1:0/0::gentoo, ebuild scheduled for
merge), Log file:
* '/var/tmp/portage/media-libs/libjpeg-turbo-2.0.1/temp/build.log'
If wanted I will post the build.log etc...
I never had an error looking like this one...
Any fox for that or am I the onlu one...?
Cheers!
Meino
How did you become root to do this emerge? If you just did "su" you
need to do "su -". Most cases I've seen of this type of sandbox
violation are because your Environment has not been sanitized. There
is something in it that leads emerge to try to do something in a place
prohibited by the sandbox.
I believe if you check for the ebuild status, it will be marked as
having completed configuration, so you could just continue with "ebuild
/path/to/ebuild/file qmerge" to complete the process.
Jack
