public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
Search results ordered by [date|relevance]  view[summary|nested|Atom feed]
thread overview below | download: 
* Re: [gentoo-user] unable to execute i386-pc-linux-gnu-gcc
  @ 2005-10-03  6:38 99%   ` Frank Schafer
  0 siblings, 0 replies; 1+ results
From: Frank Schafer @ 2005-10-03  6:38 UTC (permalink / raw
  To: gentoo-user

Maybe it's fixed. I had exactly the same problem during the installation
of python-fchksum. This is on b.g.o. too and we discussed this on
gentoo-dev a while ago. Python had the compiler it is built with hard
coded and python-fchksum was built before Python during ``emerge
system''.

I had to ``emerge --oneshot python'' before ``emerge system''. If it
works without this trick, let's hope this dependency bug is fixed now.

Regards
Frank


On Sat, 2005-10-01 at 18:37 -0400, Brett I. Holcomb wrote:
> Well, I did an emerge --emptytree system today and it all of them worked - 
> no errors.  I guess the emerge system put whatever was needed in place 
> although I do not have an i386 directory.  I was already to try your fix! 
> I'll file it for future reference.
> 
> 
>   On Sat, 1 Oct 2005, 
> heinz.sporn@sporn-it.com wrote:
> 
> >
> > Am 1.10.2005 schrieb "Brett I. Holcomb" <brettholcomb@bellsouth.net>:
> >
> >> I'm installing from a stage 1 on 2005.0 LiveCD.  I did the boot strap and
> >> a now am doing the emerge --emptytree system stage.  However, I keep
> >> getting this error on python-fchksum AND files.
> >>
> >> unable to execute i386-pc-linux-gnu-gcc: No such file or directory
> >> error: command 'i386-pc-linux-gnu-gcc' failed with exit status 1
> >>
> >
> > I had the same error here recently. I solved it by symlinking the missing
> > i386 stuff to the i686 pendants. Right now I have no access to the
> > machine where the probleme arose but IIRC I just compared the folder
> > structures of i386 with i686 and filled in the blanks so to say.
> >
> >> Checking Bugzilla showed some bugs on this but the hints given did not
> >> work - I still get the error.  That bug was marked a duplicate of another
> >> that had a long discussion on dependencies but no help on fixing it.
> >>
> >> I have not touched CHOST it is still CHOST="i686-pc-linux-gnu"
> >>
> >> Any ideas on how to fix this?
> >>
> >>
> >> --
> >>
> >> Brett I. Holcomb
> >> brettholcomb@R777bellsouth.net
> >> Registered Linux User #188143
> >> Remove R777 to email
> >> --
> >> gentoo-user@gentoo.org mailing list
> >>
> >
> >
> 
> -- 
> 
> Brett I. Holcomb
> brettholcomb@R777bellsouth.net
> Registered Linux User #188143
> Remove R777 to email
-- 
gentoo-user@gentoo.org mailing list



^ permalink raw reply	[relevance 99%]

Results 1-1 of 1 | reverse | options above
-- pct% links below jump to the message on this page, permalinks otherwise --
2005-10-01  8:58     [gentoo-user] unable to execute i386-pc-linux-gnu-gcc heinz.sporn
2005-10-01 22:37     ` Brett I. Holcomb
2005-10-03  6:38 99%   ` Frank Schafer

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox