| 1 |
thanks! adding -sandbox to FEATURES fixed this. |
| 2 |
|
| 3 |
On Tue, Jun 30, 2009 at 5:11 AM, Fabian Groffen<grobian@g.o> wrote: |
| 4 |
> On 29-06-2009 22:17:57 -0400, Michael Yang wrote: |
| 5 |
>> /home/msyang/gentoo/usr/lib/libsandbox.so(open64+0xf1)[0x2ac334bcf9c4] |
| 6 |
>> /lib64/libselinux.so.1(security_canonicalize_context_raw+0x89)[0x3496c08529] |
| 7 |
>> /lib64/libselinux.so.1[0x3496c0c6f8] |
| 8 |
>> /lib64/libselinux.so.1(matchpathcon+0xaa)[0x3496c0d8fa] |
| 9 |
>> install[0x40317a] |
| 10 |
>> /proc/28205/cmdline: install -m0755 -o 38406 -g 35 python-updater |
| 11 |
>> /home/msyang/gentoo/var/tmp/portage/app-admin/python-updater-0.6-r1/image/home/msyang/gentoo//usr/sbin |
| 12 |
> [snip] |
| 13 |
>> Here are my USE flags: |
| 14 |
>> $ echo $USE |
| 15 |
>> -berkdb -fortran -gdbm -nls -pcre -ssl |
| 16 |
>> I tried disabling selinux (by adding -selinux) in the USE flags but |
| 17 |
>> that doesn't help. |
| 18 |
> |
| 19 |
> Yeah, it's the host installed SElinux. Perhaps it's easier to just |
| 20 |
> disable sandbox (FEATURES=-sandbox). |
| 21 |
> |
| 22 |
> |
| 23 |
> -- |
| 24 |
> Fabian Groffen |
| 25 |
> Gentoo on a different level |
| 26 |
> |
| 27 |
> |
Archives