From: "Richard Fish" <bigfish@asmallpond.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] gcc upgrade and Portage questions
Date: Wed, 14 Jun 2006 14:34:21 -0700 [thread overview]
Message-ID: <7573e9640606141434h6e5039d9l3e88358269c766b0@mail.gmail.com> (raw)
In-Reply-To: <342e1090606141337v402ebe96w71e89d492796948d@mail.gmail.com>
On 6/14/06, Daniel da Veiga <danieldaveiga@gmail.com> wrote:
> On 6/14/06, Jesse Hannah <jesse.hannah@gmail.com> wrote:
> > 2. If I want to upgrade and rebuild my entire system (using a new gcc), is:
> > emerge -u gcc
> > emerge -e world
> > the right thing to do? Am I missing anything there?
>
> http://www.gentoo.org/doc/en/gcc-upgrading.xml
> Has everything you need to know...
Yes, definitely follow the guide.
During the emege -e world, if you use MAKEOPTS=-jN, where N>1, you may
notice some things fail to build (at least I did). Doing a
"MAKEOPTS=-j1 emerge -e --resume world" is the way around most
problems.
Also, if you use KDE, you may want to checkout the kdehiddenvisibility
flag before commencing the emerge -e world. Setting it should improve
KDE startup times. I can't say I noticed a dramatic speedup, but my
laptop is definitely at the high-end of the performance range...
-Richard
--
gentoo-user@gentoo.org mailing list
prev parent reply other threads:[~2006-06-14 21:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-14 20:19 [gentoo-user] gcc upgrade and Portage questions Jesse Hannah
2006-06-14 20:37 ` Daniel da Veiga
2006-06-14 21:34 ` Richard Fish [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=7573e9640606141434h6e5039d9l3e88358269c766b0@mail.gmail.com \
--to=bigfish@asmallpond.org \
--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