From: Rich Cumbers <rich.cumbers@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: apmd using wrong gcc path (FIXED)
Date: Fri, 02 Sep 2005 13:53:08 +0000 [thread overview]
Message-ID: <1125669189.482.5.camel@localhost> (raw)
In-Reply-To: <1125661861.482.2.camel@localhost>
Turns out that my gcc had not updated properly, I re emerged gcc and
libtools and all is dandy!
Is it a good idea to emerge -e world after updating gcc?
Cheers
Rich
On Fri, 2005-09-02 at 11:51 +0000, Rich Cumbers wrote:
> Hey guys
>
> I am trying to emerge gnome, however it fails on the emerge of apmd.
>
> Firstly some details of my system:
>
> amd64 running native using gcc 3.4.4
>
> The error message it spits out indicates that it is looking for gcc
> compiler verion 3.4.3:
>
> x86_64-pc-linux-gnu-g
> ++: /usr/lib/gcc/x86_64-pc-linux-gnu/3.4.3/../../../../lib64/crti.o: No
> such file or directory
>
> The file is there, but because it is using 3.4.3 it fails to find is :S
>
> So how can I get this to use 3.4.4?
>
> Thanks
>
> Rich
--
gentoo-user@gentoo.org mailing list
prev parent reply other threads:[~2005-09-02 12:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-02 11:51 [gentoo-user] apmd using wrong gcc path Rich Cumbers
2005-09-02 13:53 ` Rich Cumbers [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=1125669189.482.5.camel@localhost \
--to=rich.cumbers@gmail.com \
--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