Summary: | dev-python/pycrypto-2.0.1-r6: gcc-config error: Could not run/locate "i386-pc-linux-gnu-gcc" | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Alexander Kuznetsov <fiw> |
Component: | Hardened | Assignee: | The Gentoo Linux Hardened Team <hardened> |
Status: | VERIFIED INVALID | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Alexander Kuznetsov
2008-01-20 07:41:00 UTC
(In reply to comment #0) > building 'Crypto.Hash.MD2' extension > creating build/temp.linux-i686-2.4 > creating build/temp.linux-i686-2.4/src > i386-pc-linux-gnu-gcc -pthread -fno-strict-aliasing -DNDEBUG -march=prescott > -O2 -pipe -fforce-addr -fno-inline-functions -fPIC -Isrc/ > -I/usr/include/python2.4 -c src/MD2.c -o build/temp.linux-i686-2.4/src/MD2.o > gcc-config error: Could not run/locate "i386-pc-linux-gnu-gcc" > error: command 'i386-pc-linux-gnu-gcc' failed with exit status 1 > * > * ERROR: dev-python/pycrypto-2.0.1-r6 failed. > * Call stack: > * ebuild.sh, line 1701: Called dyn_compile > * ebuild.sh, line 1039: Called qa_call 'src_compile' > * ebuild.sh, line 44: Called src_compile > * pycrypto-2.0.1-r6.ebuild, line 39: Called distutils_src_compile > * distutils.eclass, line 48: Called die > * The specific snippet of code: > * ${python} setup.py build "$@" || die "compilation failed" > * The die message: > * compilation failed > * > * If you need support, post the topmost build error, and the call stack if > relevant. > * A complete build log is located at > '/var/tmp/portage/dev-python/pycrypto-2.0.1-r6/temp/build.log'. > * > # emerge --info > Portage 2.1.3.19 (hardened/x86/2.6, gcc-3.4.6, glibc-2.6.1-r0, 2.6.19-gentoo-r5 > i686) > ================================================================= > System uname: 2.6.19-gentoo-r5 i686 Intel(R) Celeron(R) CPU 2.53GHz > Timestamp of tree: Sat, 19 Jan 2008 01:47:01 +0000 > app-shells/bash: 3.2_p17-r1 > dev-lang/python: 2.4.3-r4 > dev-python/pycrypto: 2.0.1-r5 > sys-apps/baselayout: 1.12.10-r5 > sys-apps/sandbox: 1.2.18.1-r2 > sys-devel/autoconf: 2.60 > sys-devel/automake: 1.10 > sys-devel/binutils: 2.18-r1 > sys-devel/gcc-config: 1.4.0-r4 > sys-devel/libtool: 1.5.22 > virtual/os-headers: 2.6.23-r3 > ACCEPT_KEYWORDS="x86" > CBUILD="i686-pc-linux-gnu" > CFLAGS="-march=prescott -O2 -pipe -fforce-addr" > CHOST="i686-pc-linux-gnu" > CONFIG_PROTECT="/etc" > CONFIG_PROTECT_MASK="/etc/env.d /etc/gconf /etc/terminfo" > CXXFLAGS="-march=prescott -O2 -pipe -fforce-addr" > DISTDIR="/var/distfiles" > FEATURES="distlocks metadata-transfer sandbox sfperms strict unmerge-orphans > userfetch" > GENTOO_MIRRORS="http://osetinka.net/ http://gentoo.osuosl.org/" > MAKEOPTS="-j2" > PKGDIR="/usr/portage/packages" Well, the ebuild is right (or pycrypto is). You started of a i386 stage didn't you ? and you forgot to emerge -e system after bootstrapping from i386 to i686. So you either remerge python & pycrypto (in that order) with the new system or please pick the right stage the next time. yes, ebuild is correct. after manual emerging python and perl (next error), I have completed 'emerge -e system'. I'm getting this error also. However I downloaded a stage2-i686-2007.0.tar.bz2 tarball to install from :-( |