[gentoo-dev] Python stuff and CHOST Change don't agree

[gentoo-dev] Python stuff and CHOST Change don't agree

[Wolfgang Illmeyer]

Hi,
A few months ago I changed my CHOST in make.conf from i386-pc-linux-gnu
to i686-pc-linux-gnu. Everything went ok until I had to install some
python package; the old chost was hardcoded somewhere in
/usr/lib/python2.3 or similar and  therefore it still wanted to use the
i386-toolchain when building python stuff. remerging python didn't help.
revdep-rebuild didn't help. then I manually replaced the i386 by i686
and it went well for a while.
Today i wanted to emerge solfege with gnome useflag and it stopped at
dev-python/pyorbit due to a missing "i386-pc-linux-gnu-gcc"
what can i do?

greetings
Wolfgang
-- 
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Python stuff and CHOST Change don't agree

[Ciaran McCreesh]

[-- Attachment #1: Type: text/plain, Size: 490 bytes --]

On Thu, 28 Apr 2005 23:32:44 +0200 Wolfgang Illmeyer
<wolfgang.illmeyer@gmx.net> wrote:
| A few months ago I changed my CHOST in make.conf from
| i386-pc-linux-gnu to i686-pc-linux-gnu.

Don't do that. You need to rebuild your entire system if you're changing
CHOST, so only do it before bootstrapping a fresh install.

-- 
Ciaran McCreesh : Gentoo Developer (Vim, Fluxbox, shell tools)
Mail            : ciaranm at gentoo.org
Web             : http://dev.gentoo.org/~ciaranm


[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-dev] Python stuff and CHOST Change don't agree

[Mike Frysinger]

On Thursday 28 April 2005 05:32 pm, Wolfgang Illmeyer wrote:
> Today i wanted to emerge solfege with gnome useflag and it stopped at
> dev-python/pyorbit due to a missing "i386-pc-linux-gnu-gcc"
> what can i do?

grep your system and see what's still refering to i386 ?
-mike
-- 
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Python stuff and CHOST Change don't agree

[Robin H. Johnson]

[-- Attachment #1: Type: text/plain, Size: 730 bytes --]

On Thu, Apr 28, 2005 at 11:32:44PM +0200, Wolfgang Illmeyer wrote:
> Hi,
[snip]
> what can i do?
/sbin/fix_libtool_files.sh `gcc -dumpversion` --oldarch i386-pc-linux-gnu

If that doesn't fix it, you get to keep the pieces.

Changing the CHOST on a live system is not to be taken lightly. It's
somewhat benign on x86 boxes, but on other arches, it's practically
suicidal.

/me recalls a stupid user that thought they could change from
little-endian to big-endian by changing the CHOST.

-- 
Robin Hugh Johnson
E-Mail     : robbat2@orbis-terrarum.net
Home Page  : http://www.orbis-terrarum.net/?l=people.robbat2
ICQ#       : 30269588 or 41961639
GnuPG FP   : 11AC BA4F 4778 E3F6 E4ED  F38E B27B 944E 3488 4E85

[-- Attachment #2: Type: application/pgp-signature, Size: 241 bytes --]

Re: [gentoo-dev] Python stuff and CHOST Change don't agree

[Wolfgang Illmeyer]

Robin H. Johnson wrote:

>/sbin/fix_libtool_files.sh `gcc -dumpversion` --oldarch i386-pc-linux-gnu
>
>If that doesn't fix it, you get to keep the pieces.
>  
>
I did that together with emerge gcc glibc binutils right after changing
the CHOST, everything but python-stuff worked

>Changing the CHOST on a live system is not to be taken lightly. It's
>somewhat benign on x86 boxes, but on other arches, it's practically
>suicidal.
>
>  
>
Meanwhile I found out that libIDL had its CHOST hardcoded. The problem
wasn't about python. Remerging libIDL fixed it. I regret that I didn't
notice that before I did the emerge -e system.... I now have a working
solfege with

>/me recalls a stupid user that thought they could change from
>little-endian to big-endian by changing the CHOST.
>
>  
>
Very interesting *g*

greetings
Wolfgang
-- 
gentoo-dev@gentoo.org mailing list