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 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
somew
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.o
On Thu, 28 Apr 2005 23:32:44 +0200 Wolfgang Illmeyer
<[EMAIL PROTECTED]> 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 fre
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 build
