Summary: | sys-libs/glibc-2.21-r1: `Cannot allocate memory', while there is a plenty of free RAM | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Kristof.sno <kristof.sno+bugzilla> |
Component: | [OLD] Core system | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
Status: | RESOLVED TEST-REQUEST | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Kristof.sno
2015-07-30 02:44:47 UTC
what ulimits do you have in place ? is there anything interesting in `dmesg` ? ulimit said it's unlimited. [code] $ ulimit unlimited [/code] dmesg complained something, 9 times the same except addressing digits. [code] $ dmesg [23080085.543556] conftest[45505]: segfault at 0 ip 00007f0780c23748 sp 00007fffc590c0e0 error 4 in conftest[7f0780c23000+1000] [23080085.944313] conftest[45531]: segfault at 0 ip 00007fdf5f5739aa sp 00007fff846ae068 error 4 in libc-2.19.so[7fdf5f4d8000+1b1000] [/code] I confess, however, that I tried many times and many ways to build glibc and so on and thus I am not confident if it was for glibc build. Besides the above error, only messages are for mounting file systems. try disabling the sandbox: FEATURES='-sandbox -usersandbox' emerge ... |