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