From: "Daniel da Veiga" <danieldaveiga@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] gcc upgrade and Portage questions
Date: Wed, 14 Jun 2006 17:37:17 -0300 [thread overview]
Message-ID: <342e1090606141337v402ebe96w71e89d492796948d@mail.gmail.com> (raw)
In-Reply-To: <200606141319.03953.jesse.hannah@gmail.com>
On 6/14/06, Jesse Hannah <jesse.hannah@gmail.com> wrote:
> 1. Has anyone noticed if programs compiled with the latest gcc (4.1.1, I
> believe) are any faster than those compiled with 3.4.6-r1? Also, is there any
> difference in the required time to compile? Any other issues I should know
> about with upgrading from 3.4.6-r1 to 4.1.1? (I use a pre-Prescott P4
> 3000MHz, so it'd be nice if anyone had information for that or a comparable
> architecture.)
>
I didn't notice any speed change after recompiling.
> 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...
>
> (Note: if it makes any difference, I have ACCEPT_KEYWORDS="~x86" set in
> my /etc/make.conf. Any problems this could cause?)
So do I. So far, so good... Except that I use binary openoffice.
--
Daniel da Veiga
Computer Operator - RS - Brazil
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GCM/IT/P/O d-? s:- a? C++$ UBLA++ P+ L++ E--- W+++$ N o+ K- w O M- V-
PS PE Y PGP- t+ 5 X+++ R+* tv b+ DI+++ D+ G+ e h+ r+ y++
------END GEEK CODE BLOCK------
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-06-14 20:46 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 [this message]
2006-06-14 21:34 ` Richard Fish
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=342e1090606141337v402ebe96w71e89d492796948d@mail.gmail.com \
--to=danieldaveiga@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