1 |
hi! |
2 |
|
3 |
emerge return errors during build of any atoms in linux32 chroot only. |
4 |
|
5 |
(null)*(null) (null)ACCESS DENIED(null): open_wr: /dev/tty |
6 |
(null)*(null) (null)ACCESS DENIED(null): open_wr: /dev/null |
7 |
|
8 |
The full log http://pastebin.com/4An1ajY0 |
9 |
|
10 |
stat /dev/{null,tty} |
11 |
File: '/dev/null' |
12 |
Size: 0 Blocks: 0 IO Block: 4096 character |
13 |
special file |
14 |
Device: 5h/5d Inode: 1028 Links: 1 Device type: 1,3 |
15 |
Access: (0666/crw-rw-rw-) Uid: ( 0/ root) Gid: ( 0/ root) |
16 |
|
17 |
File: '/dev/tty' |
18 |
Size: 0 Blocks: 0 IO Block: 4096 character |
19 |
special file |
20 |
Device: 5h/5d Inode: 1035 Links: 1 Device type: 5,0 |
21 |
Access: (0666/crw-rw-rw-) Uid: ( 0/ root) Gid: ( 5/ tty) |
22 |
|
23 |
Kernel 3.11.7-hardened-r1 |
24 |
Kernel config |
25 |
zcat /proc/config.gz | grep -i -e grkern -e pax |
26 |
http://pastebin.com/ka63Jf98 |
27 |
|
28 |
emerge --info |
29 |
http://pastebin.com/WJ7BRXCA |
30 |
|
31 |
|
32 |
In x86_64 chroot all works fine. Also, with hardened-sources-3.2.52-r3 |
33 |
linux32 chroot works fine too. |
34 |
Please suggest any solution. |