1 |
This is a known bug. This is from the x86 how-to |
2 |
(www.bulah.com/embeddedgentoo.html). Try this: |
3 |
# Workaround 2 |
4 |
# During emerge -e system, python-fchksum failes complaing about |
5 |
# gcc-config error: Could not run/locate "i386-gentoo-linux-uclibc-gcc" |
6 |
# The following commands work around this problem. |
7 |
emerge python |
8 |
emerge -e system |
9 |
|
10 |
-- |
11 |
heath holcomb |
12 |
liquidcable at bulah.com |
13 |
www.bulah.com |
14 |
|
15 |
|
16 |
On Wednesday 06 July 2005 09:45 am, Tim Lapawa wrote: |
17 |
> Hello list, |
18 |
> I am getting into trouble with the emerge -e system command. |
19 |
> After following the HOWTO 0.4 |
20 |
> (http://www.mail-archive.com/gentoo-embedded@l.g.o/msg00082.html |
21 |
>) |
22 |
> |
23 |
> The build process stops at the python-fchksum ebuild with this message: |
24 |
> >>> emerge (16 of 72) dev-python/python-fchksum-1.7.1 to / |
25 |
> >>> md5 files ;-) ChangeLog |
26 |
> >>> md5 files ;-) metadata.xml |
27 |
> >>> md5 files ;-) python-fchksum-1.6.1-r1.ebuild |
28 |
> >>> md5 files ;-) python-fchksum-1.7.1.ebuild |
29 |
> >>> md5 files ;-) files/digest-python-fchksum-1.6.1-r1 |
30 |
> >>> md5 files ;-) files/digest-python-fchksum-1.7.1 |
31 |
> >>> md5 src_uri ;-) python-fchksum-1.7.1.tar.gz |
32 |
> >>> Unpacking source... |
33 |
> >>> Unpacking python-fchksum-1.7.1.tar.gz to |
34 |
> >>> /var/tmp/portage/python-fchksum-1.7.1/work Source unpacked. |
35 |
> |
36 |
> ['setup.py', 'build'] |
37 |
> running build |
38 |
> running build_ext |
39 |
> building 'fchksum' extension |
40 |
> creating build |
41 |
> creating build/temp.linux-i686-2.3 |
42 |
> i386-gentoo-linux-uclibc-gcc -pthread -fno-strict-aliasing -DNDEBUG |
43 |
> -march=c3 -Os -pipe -fomit-frame-pointer -m3dnow -fPIC |
44 |
> -I/usr/include/python2.3 -c md5.c -o build/temp.linux-i686-2.3/md5.o |
45 |
> gcc-config error: Could not run/locate "i386-gentoo-linux-uclibc-gcc" |
46 |
> error: command 'i386-gentoo-linux-uclibc-gcc' failed with exit status 1 |
47 |
> |
48 |
> |
49 |
> All the preceding ebuilds used i586-gentoo-linux-uclibc-gcc to compile |
50 |
> an succeded. Why does the python-fchksum package use the i384 gcc? |
51 |
> It is not availble in /usr/bin on the chroot environment. |
52 |
> Can I force ebuild to use the i586 compiler like the other packages do? |
53 |
> Here is the make.conf file, too: |
54 |
> |
55 |
> USE="uclibc" |
56 |
> CHOST="i586-gentoo-linux-uclibc" |
57 |
> CFLAGS="-march=c3 -Os -pipe -fomit-frame-pointer -m3dnow" |
58 |
> CXXFLAGS=${CFLAGS} |
59 |
> FEATURES="buildpkg" |
60 |
> |
61 |
> |
62 |
> Thanks for any hints. |
63 |
> Best regards |
64 |
> Tim |
65 |
> |
66 |
> |
67 |
> |
68 |
> |
69 |
> |
70 |
> |
71 |
> -- |
72 |
> \\\/// |
73 |
> Tim Lapawa (o -) tim@××××××.net |
74 |
> -------------oo0-(_)-0oo---------------------- |
75 |
> ,ooo0 Where do you want |
76 |
> ( ) 0ooo, to go tomorrow? |
77 |
> ---\ (---------( )---------------------- |
78 |
> \ _ ) ) / |
79 |
> ( _ / |
80 |
|
81 |
-- |
82 |
gentoo-embedded@g.o mailing list |