Summary: | sys-libs/glibc-2.10.1-r1 build error: ld-linux.so.2: cannot execute binary file | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Ricardo Fabbri <rfabbri> |
Component: | [OLD] Core system | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | jaak |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Ricardo Fabbri
2010-03-11 01:43:51 UTC
see if turning off sandbox makes a difference: FEATURES=-sandbox also make sure you arent setting weird mount perms or disabled 32bit support in the kernel Enabling 32-bit support in kernel worked around the problem for me, although I actually wanted to switch to no-multilib. I encountered this bug and was able to complete the glibc emerge by setting IA32_EMULATION=y and IA32_AOUT=y in the kernel. Is there a pressing reason why glibc needs to use 32bit binaries? you cant enable multilib support in userspace and disable 32bit support in the kernel. this is a misconfiguration in your system, not a bug in glibc. (In reply to comment #5) > you cant enable multilib support in userspace and disable 32bit support in the > kernel. this is a misconfiguration in your system, not a bug in glibc. So one can't build a multilib glibc when not running a kernel with 32-bit support? If this is really inevitable, maybe the ebuild should check the config of the running kernel before attempting the build to provide users with better error messages. I think it should at least output a warning before the compile. |