From: Jarry <mr.jarry@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] gcc upgrade: Active gcc profile is invalid!
Date: Tue, 19 Oct 2010 20:57:18 +0200 [thread overview]
Message-ID: <4CBDEA0E.5030004@gmail.com> (raw)
In-Reply-To: <20101019180221.GB2287@Caemlyn.diku.dk>
On 19. 10. 2010 20:02, Zeerak Mustafa Waseem wrote:
> On Tue, Oct 19, 2010 at 07:45:58PM +0200, Jarry wrote:
>> I just tried to upgrade gcc (stable amd64, from 4.4.3-r2
>> to 4.4.4-r2) following the procedure recommended in Gentoo
>> GCC Upgrade Guide:
>>
>> emerge -uav gcc
>>
>> At the end of compilation, I got these strange messages:
>> ====================================================
>> * gcc-config: Could not locate 'x86_64-pc-linux-gnu-4.4.3'
>> in '/etc/env.d/gcc/'
>> !
> <snip>
>> * Please re-emerge gcc.
>> * http://bugs.gentoo.org/68395
> <snip>
>
> That should do it :)
Thanks, "emerge --oneshot gcc" really seems to have fixed it.
I just think it is somehow time-consuming, emerging gcc two times.
Especially when I have to repeat it with my 12 gentoo servers.
Sequentially, unfortunatally, as they share the same hardware...
Jarry
--
_______________________________________________________________
This mailbox accepts e-mails only from selected mailing-lists!
Everything else is considered to be spam and therefore deleted.
next prev parent reply other threads:[~2010-10-19 19:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-19 17:45 [gentoo-user] gcc upgrade: Active gcc profile is invalid! Jarry
2010-10-19 18:02 ` Zeerak Mustafa Waseem
2010-10-19 18:57 ` Jarry [this message]
2010-10-19 19:04 ` [gentoo-user] " Nikos Chantziaras
2010-10-19 20:07 ` [gentoo-user] " Neil Bothwick
2010-10-20 10:10 ` 李健
2010-10-21 17:35 ` Jarry
2010-10-21 18:38 ` Dale
2010-10-21 21:58 ` [gentoo-user] " Nikos Chantziaras
2010-10-19 18:59 ` [gentoo-user] " Tanstaafl
2010-10-19 19:02 ` Andrea Conti
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=4CBDEA0E.5030004@gmail.com \
--to=mr.jarry@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