Summary: | bootstrap from stage1 fails on Python build; g++ not found | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Damian Gerow <dgerow> |
Component: | Current packages | Assignee: | Python Gentoo Team <python> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Damian Gerow
2005-03-07 14:20:29 UTC
As per conversation in IRC, I added "--with-cxx=no" to the econf section of the Python 2.3.4-r1 ebuild. It now fails telling me that '"/lib/cpp" fails sanity check'. config.log complains a few times about: /usr/include/bits/local_lim.h:36:26: linux/limits.h: No such file or directory once about: conftest.c:2: error: syntax error before "me" configure:2619: $? = 1 configure: failed program was: | #ifndef __cplusplus | choke me | #endif and a few times about: /usr/include/sys/cdefs.h:31: #error "You need a ISO C conforming compiler to use the glibc headers" When I try to run /lib/cpp directly: livecd lib # /lib/cpp Could not run/locate "cpp" livecd lib # Note that this is all from within the chroot. If I run /lib/cpp from outside the chroot, it seems to operate just fine. Left the versions of everyone out in the initial bug report: LiveCD: 20040616-1 Stage1: 20041123 Portage: 20050306 this really cant be solved without more info cpp and linux headers both exist in stage1 ... what you've shown is that for some reason they no longer existed on your machine |