From: Nikos Chantziaras <realnc@arcor.de>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: gcc upgrade: Active gcc profile is invalid!
Date: Fri, 22 Oct 2010 00:58:58 +0300 [thread overview]
Message-ID: <i9qd2t$mp6$2@dough.gmane.org> (raw)
In-Reply-To: <4CC079FC.6090502@gmail.com>
On 10/21/2010 08:35 PM, Jarry wrote:
> On 19. 10. 2010 22:07, Neil Bothwick wrote:
>> On Tue, 19 Oct 2010 20:57:18 +0200, Jarry wrote:
>>> Especially when I have to repeat it with my 12 gentoo servers.
>>> Sequentially, unfortunatally, as they share the same hardware...
>>
>> Why not use --buildpkg the first time and --usepkg the other 11 times?
>
> They have slightly different use-flags. But I do not know if some
> of them might have impact on gcc too...
I already mentioned in another post that you don't need to build gcc
twice and the message that tells you to do so is wrong.
next prev parent reply other threads:[~2010-10-21 22:09 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
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 ` Nikos Chantziaras [this message]
2010-10-19 18:59 ` 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='i9qd2t$mp6$2@dough.gmane.org' \
--to=realnc@arcor.de \
--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