Re: [gentoo-catalyst] python-fchksum error - looking for wrong gcc? (was: specifying global USE)

[bob p]

On Apr 3, 2005 6:34 AM, Jeff Davidson <supermonkey@×××××.com> wrote:

> And now for a more annoying problem:  My stage3 fails on
> python-fchksum, which for some odd reason was trying to use
> i386-pc-linux-gnu-gcc instead of the i686 gcc I have installed.  In
> the catalyst-generated tarball, there were two i386-pc gcc files that
> I thought were generating this error, but when I removed them and
> retarred the file I still got it (although it changed from gcc-config
> complaining to a simple file not found):

Hi.  I'm new to the list.

Jeff, I've seen this problem before.  Ryan (Sith) had commented that
he had also seen the problem with python-fchksum occurring when he was
rebuilding a GCC 343 toolkit on a 2005.0 installation.  He said that,
"the ebuild compiles using python, and if python has been compiled
using an older gcc compiler, then it uses that compiler to build
python-fchsum, which causes cflag problems (with -mtune)."
Interestingly, he only noticed this problem occurring with the x86
stageball and not any of the stageballs based on i686.

I'm thinking that this problem could be caused by the retention of
static libraries from the previous version of GCC.  I would try
"emerge -e system && emerge -e system" and see if that makes the
problem go away.

Just an idea.  I hope it works.

bob
--
gentoo-catalyst@g.o mailing list