From: Frank Schafer <frank.schafer@t-systems.cz>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] unable to execute i386-pc-linux-gnu-gcc
Date: Mon, 03 Oct 2005 08:38:46 +0200 [thread overview]
Message-ID: <1128321526.5760.7.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.63.0510011836410.4366@gandalf>
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
prev parent reply other threads:[~2011-10-31 3:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-01 2:22 [gentoo-user] unable to execute i386-pc-linux-gnu-gcc Brett I. Holcomb
2005-10-01 3:25 ` Dave Nebinger
2005-10-01 4:10 ` Brett I. Holcomb
2005-10-01 8:58 ` heinz.sporn
2005-10-01 16:15 ` Brett I. Holcomb
2005-10-01 22:37 ` Brett I. Holcomb
2005-10-03 6:38 ` Frank Schafer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1128321526.5760.7.camel@localhost.localdomain \
--to=frank.schafer@t-systems.cz \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox