1 |
Hi, |
2 |
|
3 |
It was interesting trying to hack into this problem :-) |
4 |
And now I understand the exact problem and see a couple |
5 |
of ways to eradicate the very ugly |
6 |
# emerge -e system ; emerge python ; emerge -e system |
7 |
step from Heath's how to. |
8 |
|
9 |
First, you can see why this happens in my comment to |
10 |
the bug you pointed me too (bug #88777). |
11 |
|
12 |
And the solution's I see for Heath's how to (the ones |
13 |
I consider reasonables) are: |
14 |
|
15 |
- edit /usr/lib/python2.3/config/Makefile changing: |
16 |
from "CC= i386-gentoo-linux-uclibc-gcc -pthread" |
17 |
to "CC= gcc -pthread" at line #32 |
18 |
|
19 |
- apply the attached patch to automate this change. |
20 |
# cd / && patch -p0 < path/to/python.patch |
21 |
|
22 |
This two options can be followed at any point in Heath's |
23 |
how to up to just before the emerge -e system step. |
24 |
|
25 |
- Try using stage1-x86-uclibc-2004.3.tar.bz2 instead |
26 |
of stage1-x86-uclibc-2005.0.tar.bz2 as it should not |
27 |
suffer form this problem. |
28 |
|
29 |
- Hope that this problem will be solved soon (possibly |
30 |
with the solution I give in my comment to the bug). |
31 |
|
32 |
Best wishes, |
33 |
Yuri. |
34 |
|
35 |
On Thu, 9 Jun 2005 08:25:39 -0500 |
36 |
Heath H Holcomb <liquidcable@×××××.com> wrote: |
37 |
|
38 |
> Sorry for the long delay. Here is the output of the emerge -e system on the |
39 |
> first attempt. |
40 |
> |
41 |
> >>> emerge (13 of 66) dev-python/python-fchksum-1.7.1 to / |
42 |
> >>> md5 files ;-) python-fchksum-1.7.1.ebuild |
43 |
> >>> md5 files ;-) python-fchksum-1.6.1-r1.ebuild |
44 |
> >>> md5 files ;-) ChangeLog |
45 |
> >>> md5 files ;-) metadata.xml |
46 |
> >>> md5 files ;-) files/digest-python-fchksum-1.7.1 |
47 |
> >>> md5 files ;-) files/digest-python-fchksum-1.6.1-r1 |
48 |
> >>> md5 src_uri ;-) python-fchksum-1.7.1.tar.gz |
49 |
> >>> Unpacking source... |
50 |
> >>> Unpacking python-fchksum-1.7.1.tar.gz |
51 |
> to /var/tmp/portage/python-fchksum-1.7.1/work |
52 |
> >>> Source unpacked. |
53 |
> ['setup.py', 'build'] |
54 |
> running build |
55 |
> running build_ext |
56 |
> building 'fchksum' extension |
57 |
> creating build |
58 |
> creating build/temp.linux-i686-2.3 |
59 |
> i386-gentoo-linux-uclibc-gcc -pthread -fno-strict-aliasing -DNDEBUG |
60 |
> -march=i586 -Os -pipe -fomit-frame-pointer -mmmx -fPIC |
61 |
> -I/usr/include/python2.3 -c md5.c -o build/temp.linux-i686-2.3/md5.o |
62 |
> gcc-config error: Could not run/locate "i386-gentoo-linux-uclibc-gcc" |
63 |
> error: command 'i386-gentoo-linux-uclibc-gcc' failed with exit status 1 |
64 |
> |
65 |
> !!! ERROR: dev-python/python-fchksum-1.7.1 failed. |
66 |
> !!! Function src_compile, Line 20, Exitcode 1 |
67 |
> !!! (no error message) |
68 |
> !!! If you need support, post the topmost build error, NOT this status |
69 |
> message. |
70 |
> |
71 |
> |
72 |
> It seams to be bug 88777. |
73 |
> http://bugs.gentoo.org/show_bug.cgi?id=88777 |
74 |
> |
75 |
> I found the work around in the Gentoo forums. |
76 |
> http://forums.gentoo.org/viewtopic-t-314985-start-401.html |
77 |
> |
78 |
> The problem is repeatable (every time) with the steps in my x86 how-to. The |
79 |
> "workaround" works every time. |
80 |
> |
81 |
> |
82 |
> -- |
83 |
> Heath Holcomb |
84 |
> liquidcable |
85 |
> liquidcable at bulah.com |