all i did was set CHOST to "i586-gentoo-linux-uclibc". bootstrap completes, but 'emerge -e system' fails when it tries to merge dev-python/python-fchksum. it appears the failure is because it tries to use i386...gcc to compile it. i note that the package merged directly before python-fchksum, zlib, was built using i586...gcc. >>> emerge (9 of 70) dev-python/python-fchksum-1.7.1 to / >>> md5 files ;-) python-fchksum-1.7.1.ebuild >>> md5 files ;-) python-fchksum-1.6.1-r1.ebuild >>> md5 files ;-) ChangeLog >>> md5 files ;-) metadata.xml >>> md5 files ;-) files/digest-python-fchksum-1.7.1 >>> md5 files ;-) files/digest-python-fchksum-1.6.1-r1 >>> md5 src_uri ;-) python-fchksum-1.7.1.tar.gz >>> Unpacking source... >>> Unpacking python-fchksum-1.7.1.tar.gz to /var/tmp/portage/python-fchksum-1.7.1/work >>> Source unpacked. ['setup.py', 'build'] running build running build_ext building 'fchksum' extension creating build creating build/temp.linux-i686-2.3 i386-gentoo-linux-uclibc-gcc -pthread -fno-strict-aliasing -DNDEBUG -Os -pipe -fPIC -I/usr/include/python2.3 -c md5.c -o build/temp.linux-i686-2.3/md5.o gcc-config error: Could not run/locate "i386-gentoo-linux-uclibc-gcc" error: command 'i386-gentoo-linux-uclibc-gcc' failed with exit status 1 !!! ERROR: dev-python/python-fchksum-1.7.1 failed. !!! Function src_compile, Line 22, Exitcode 1 !!! (no error message) !!! If you need support, post the topmost build error, NOT this status message. Reproducible: Always Steps to Reproduce: mkdir /mnt/uc; cd /mnt/uc tar xjpf /tmp/stage1-x86-uclibc-2005.0.tar.bz2 mkdir /mnt/uc/usr/portage mount -o bind /usr/portage /mnt/uc/usr/portage mount -o bind /proc /mnt/uc/proc cp /etc/resolv.conf /mnt/uc/etc chroot /mnt/uc /bin/bash env-update source /etc/profile #edit make.conf (change CHOST to i586-gentoo-linux-uclibc) cd /usr/portage scripts/bootstrap.sh env-update; source /etc/profile (who knows, it was suggested to me - makes no difference in results) emerge -e system Actual Results: >>> emerge (9 of 70) dev-python/python-fchksum-1.7.1 to / >>> md5 files ;-) python-fchksum-1.7.1.ebuild >>> md5 files ;-) python-fchksum-1.6.1-r1.ebuild >>> md5 files ;-) ChangeLog >>> md5 files ;-) metadata.xml >>> md5 files ;-) files/digest-python-fchksum-1.7.1 >>> md5 files ;-) files/digest-python-fchksum-1.6.1-r1 >>> md5 src_uri ;-) python-fchksum-1.7.1.tar.gz >>> Unpacking source... >>> Unpacking python-fchksum-1.7.1.tar.gz to /var/tmp/portage/python-fchksum-1.7.1/work >>> Source unpacked. ['setup.py', 'build'] running build running build_ext building 'fchksum' extension creating build creating build/temp.linux-i686-2.3 i386-gentoo-linux-uclibc-gcc -pthread -fno-strict-aliasing -DNDEBUG -Os -pipe -fPIC -I/usr/include/python2.3 -c md5.c -o build/temp.linux-i686-2.3/md5.o gcc-config error: Could not run/locate "i386-gentoo-linux-uclibc-gcc" error: command 'i386-gentoo-linux-uclibc-gcc' failed with exit status 1 !!! ERROR: dev-python/python-fchksum-1.7.1 failed. !!! Function src_compile, Line 22, Exitcode 1 !!! (no error message) !!! If you need support, post the topmost build error, NOT this status message. Expected Results: used i586-gentoo-linux-uclibc-gcc instead, i think both dev-fchksum and python are already installed (same versions its trying to merge) before 'emerge -e system' starts. the fchksum module is being merged by 'emerge -e system' before python itself, but i'm not sure if this matters. # gcc-config -l [1] i586-gentoo-linux-uclibc-3.3.5-20050130 * [2] i586-gentoo-linux-uclibc-3.3.5-20050130-hardened [3] i586-gentoo-linux-uclibc-3.3.5-20050130-hardenednopie [4] i586-gentoo-linux-uclibc-3.3.5-20050130-hardenednossp # emerge info Portage 2.0.51.19 (uclibc/x86/2.4, gcc-3.3.5-20050130, uclibc-0.9.27-r0, 2.6.11-ck2 i686) ================================================================= System uname: 2.6.11-ck2 i686 Intel(R) Pentium(R) 4 CPU 2.40GHz Gentoo Base System version 1.4.16 Python: dev-lang/python-2.3.4-r1 [2.3.4 (#1, Apr 16 2005, 06:03:45)] dev-lang/python: 2.3.4-r1 sys-devel/autoconf: [Not Present] sys-devel/automake: [Not Present] sys-devel/binutils: 2.15.92.0.2-r7 sys-devel/libtool: [Not Present] virtual/os-headers: 2.4.22-r1 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-Os -pipe" CHOST="i586-gentoo-linux-uclibc" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-Os -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks nodoc noinfo noman sandbox sfperms strict" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 berkdb ncurses python readline uclibc zlib" Unset: ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTDIR_OVERLAY
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
*** This bug has been marked as a duplicate of 88777 ***
