Summary: | emerge -e system fails with stage1-x86-uclibc-2005.0.tar.bz2 ( embedded ) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | daniel reznick <offbyone> |
Component: | [OLD] Unspecified | Assignee: | Embedded Gentoo Team <embedded> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | |
Priority: | High | ||
Version: | 2005.0 | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
daniel reznick
2005-04-18 09:07:10 UTC
run `gcc-config 1 && source /etc/profile` and see if the problem goes away i notice that i can get the system to build if i do a 'emerge --newuse system' after bootstrapping. subsequent 'emerge -e system' will complete. I used a stage1-x86-uclibc-hardened-2005.0.tar.bz2 from April 17th and chose the uclibc/x86/hardened profile. In /etc/make.conf, I had CHOST="i686-gentoo-linux- uclibc", and during emerge -e system I had the same problem. gcc-config 1 && source /etc/profile didn't help. What did the trick for me was emerge -O python (which is probably done by emerge --newuse system.) Regards, Milan |