Hi,
It was interesting trying to hack into this problem :-)
And now I understand the exact problem and see a couple
of ways to eradicate the very ugly
# emerge -e system ; emerge python ; emerge -e system
step from Heath's how to.
First, you can see why this happens in my comment to
the bug you pointed me too (bug #88777).
And the solution's I see for Heath's how to (the ones
I consider reasonables) are:
- edit /usr/lib/python2.3/config/Makefile changing:
from "CC= i386-gentoo-linux-uclibc-gcc -pthread"
to "CC= gcc -pthread" at line #32
- apply the attached patch to automate this change.
# cd / && patch -p0 < path/to/python.patch
This two options can be followed at any point in Heath's
how to up to just before the emerge -e system step.
- Try using stage1-x86-uclibc-2004.3.tar.bz2 instead
of stage1-x86-uclibc-2005.0.tar.bz2 as it should not
suffer form this problem.
- Hope that this problem will be solved soon (possibly
with the solution I give in my comment to the bug).
Best wishes,
Yuri.
On Thu, 9 Jun 2005 08:25:39 -0500
Heath H Holcomb <[EMAIL PROTECTED]> wrote:
> Sorry for the long delay. Here is the output of the emerge -e system on the
> first attempt.
>
> >>> emerge (13 of 66) 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
> -march=i586 -Os -pipe -fomit-frame-pointer -mmmx -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 20, Exitcode 1
> !!! (no error message)
> !!! If you need support, post the topmost build error, NOT this status
> message.
>
>
> It seams to be bug 88777.
> http://bugs.gentoo.org/show_bug.cgi?id=88777
>
> I found the work around in the Gentoo forums.
> http://forums.gentoo.org/viewtopic-t-314985-start-401.html
>
> The problem is repeatable (every time) with the steps in my x86 how-to. The
> "workaround" works every time.
>
>
> --
> Heath Holcomb
> liquidcable
> liquidcable at bulah.com
--- usr/lib/python2.3/config/Makefile.orig 2005-06-09 19:36:03.000000000 -0500
+++ usr/lib/python2.3/config/Makefile 2005-06-09 19:38:02.000000000 -0500
@@ -29,7 +29,7 @@
srcdir= .
-CC= i386-gentoo-linux-uclibc-gcc -pthread
+CC= gcc -pthread
CXX=
LINKCC= $(PURIFY) $(CC)
AR= ar
