| Summary: | dev-libs/klibc chooses ARCH based on running kernel rather than userland or ARCH parameter | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Jarl Stefansson <jarl> |
| Component: | [OLD] Library | Assignee: | Christian Heim (RETIRED) <phreak> |
| Status: | RESOLVED NEEDINFO | ||
| Severity: | normal | CC: | kernel |
| Priority: | High | ||
| Version: | 2006.1 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
(In reply to comment #0) > Emerging klibc in an i386 userland on an x86_64 kernel returns: > "sorry, unimplemented: 64-bit mode not compiled in" > > The kernel sources are built using ARCH="i386" and the useland utilities are > inside a chroot, only the host kernel is x86_64. > > Klibc Makefile uses uname -m to determine the target architecture and ignores > the ARCH parameter. > > I think the best solution would be to add support for the ARCH parameter so > that klibc behaves like the kernel packages. Guess you should take a look at CTARGET and/or CBUILD, as thats being utilized in the ebuild. If you have them set correctly, please report back. |
Emerging klibc in an i386 userland on an x86_64 kernel returns: "sorry, unimplemented: 64-bit mode not compiled in" The kernel sources are built using ARCH="i386" and the useland utilities are inside a chroot, only the host kernel is x86_64. Klibc Makefile uses uname -m to determine the target architecture and ignores the ARCH parameter. I think the best solution would be to add support for the ARCH parameter so that klibc behaves like the kernel packages.