1 |
On 2018.11.13 12:11, tuxic@××××××.de wrote: |
2 |
> Hi, |
3 |
> |
4 |
> I got a weird looking error while upgrading/recompiling nasm: |
5 |
[snip....] |
6 |
> -- Configuring done |
7 |
> -- Generating done |
8 |
> -- Build files have been written to: |
9 |
> /var/tmp/portage/media-libs/libjpeg-turbo-2.0.1/work/libjpeg-turbo-2.0.1-abi_x86_64.amd64 |
10 |
> >>> Source configured. |
11 |
> * --------------------------- ACCESS VIOLATION SUMMARY |
12 |
> --------------------------- |
13 |
> * LOG FILE: "/var/log/sandbox/sandbox-16492.log" |
14 |
> * |
15 |
> VERSION 1.0 |
16 |
> FORMAT: F - Function called |
17 |
> FORMAT: S - Access Status |
18 |
> FORMAT: P - Path as passed to function |
19 |
> FORMAT: A - Absolute Path (not canonical) |
20 |
> FORMAT: R - Canonical Path |
21 |
> FORMAT: C - Command Line |
22 |
> |
23 |
> F: fopen_wr |
24 |
> S: deny |
25 |
> P: /? |
26 |
> A: /? |
27 |
> R: /? |
28 |
> C: /usr/bin/nasm /? |
29 |
> * |
30 |
> -------------------------------------------------------------------------------- |
31 |
> !!! When you file a bug report, please include the following |
32 |
> information: |
33 |
> GENTOO_VM= CLASSPATH="" JAVA_HOME="" |
34 |
> JAVACFLAGS="" COMPILER="" |
35 |
> and of course, the output of emerge --info =libjpeg-turbo-2.0.1 |
36 |
> * |
37 |
> * The following package has failed to build, install, or execute |
38 |
> postinst: |
39 |
> * |
40 |
> * (media-libs/libjpeg-turbo-2.0.1:0/0::gentoo, ebuild scheduled for |
41 |
> merge), Log file: |
42 |
> * '/var/tmp/portage/media-libs/libjpeg-turbo-2.0.1/temp/build.log' |
43 |
> |
44 |
> |
45 |
> If wanted I will post the build.log etc... |
46 |
> |
47 |
> I never had an error looking like this one... |
48 |
> |
49 |
> Any fox for that or am I the onlu one...? |
50 |
> |
51 |
> Cheers! |
52 |
> Meino |
53 |
How did you become root to do this emerge? If you just did "su" you |
54 |
need to do "su -". Most cases I've seen of this type of sandbox |
55 |
violation are because your Environment has not been sanitized. There |
56 |
is something in it that leads emerge to try to do something in a place |
57 |
prohibited by the sandbox. |
58 |
|
59 |
I believe if you check for the ebuild status, it will be marked as |
60 |
having completed configuration, so you could just continue with "ebuild |
61 |
/path/to/ebuild/file qmerge" to complete the process. |
62 |
|
63 |
Jack |