From: "Bob Young" <BYoung@nucoretech.com>
To: <gentoo-user@lists.gentoo.org>
Subject: RE: [gentoo-user] gcc-4.1.1
Date: Mon, 12 Jun 2006 14:35:54 -0700 [thread overview]
Message-ID: <FAEEIJPAOFEMBBLKPMJEEEJIGDAA.BYoung@NuCORETech.com> (raw)
In-Reply-To: <200606072210.11564.mcbrides9@comcast.net>
> -----Original Message-----
> From: Jerry McBride [mailto:mcbrides9@comcast.net]
> Sent: Wednesday, June 07, 2006 7:10 PM
> To: gentoo-user@lists.gentoo.org
> Subject: Re: [gentoo-user] gcc-4.1.1
>
>
> On Wednesday 07 June 2006 21:50, Bob Young wrote:
> Note that the
> > article does in the end, do a double emerge -e system, so the
> the value of
> > updating a toolchain subset is questionable for the article's purposes.
> >
> > In short:
> >
> > emerge gcc-config glibc binutils libstdc++-v3 gcc
> > emerge gcc-config glibc binutils libstdc++-v3 gcc
> > emerge -e world
> >
> > To be clear, in order to make sure absolutely everything is
> updated and the
> > libraries that are linked against are also updated prior to use, the two
> > emerge -e system commands, are the definitive solution. For
> those who don't
> > want to spend many extra hours of compile time, in order to gain a 0.5%
> > increase in performance, the above is offered for consideration.
> >
> > Regards,
> > Bob Young
>
> Wow! I said the same thing a week or so ago and got the same rebuttal.
> However, it's what I do none the less. And it works.
>
I've been thinking about this over the last week or so. In particular the
fact that gcc always uses itself to build itself, does elminate the need for
building gcc twice. That being the case, emerging the new gcc then selecting
it as the default system compiler followed by a single emerge -e world
should be all that is necessary. I suppose it's possible that a few apps or
utilities that use static linking *could* possibly end up linking against
libraries that have not been rebuilt with the new compiler yet due to build
order issues. However since the number of apps and utilities that actually
use static linking is very small, it doesn't seem that a double emerge -e
world or system is justified.
That being said, seems these two articles appear to be giving out bad
information:
http://forums.gentoo.org/viewtopic.php?t=282474&highlight=
http://forums.gentoo.org/viewtopic-t-345229.html
If I've mis-characterisized the issue in the above description I'd
appreciate it if someone would correct any mis-statements. Lastly, since the
Gentoo handbook no longer describes a stage one install, is there any
"official" documentation that describes the *correct* way to do a stage3
install and end up with the same level of optimization and customization
that used to be provided by a stage1 install?
--
Regards,
Bob Young
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-06-12 21:43 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ad4496950606070647s5a4bc702m8deeda7dbd590c4a@mail.gmail.com>
2006-06-07 13:53 ` [gentoo-user] gcc-4.1.1 Mohammed Hagag
2006-06-07 14:30 ` Peper
2006-06-07 14:35 ` Julien Cabillot
2006-06-07 14:45 ` Kristian Poul Herkild
2006-06-07 14:56 ` Neil Bothwick
2006-06-07 15:00 ` Bo Ørsted Andresen
2006-06-07 15:25 ` Conneries wearegeeks
2006-06-07 16:04 ` Roy Wright
2006-06-07 17:46 ` Mike Huber
2006-06-07 18:09 ` Daniel da Veiga
2006-06-07 19:27 ` Roy Wright
2006-06-07 19:55 ` Daniel da Veiga
2006-06-07 18:17 ` Evan Klitzke
2006-06-07 23:25 ` Richard Fish
2006-06-08 0:32 ` Evan Klitzke
2006-06-08 4:40 ` Richard Fish
2006-06-08 11:39 ` Mohammed Hagag
2006-06-08 1:50 ` Bob Young
2006-06-08 2:10 ` Jerry McBride
2006-06-12 21:35 ` Bob Young [this message]
2006-06-13 0:09 ` Richard Fish
2006-06-08 4:24 ` Richard Fish
2006-06-08 12:34 ` Bob Young
2006-06-08 13:31 ` Hans-Werner Hilse
2006-06-08 14:00 ` Bob Young
2006-06-08 14:28 ` Bo Ørsted Andresen
2006-06-08 14:57 ` Bob Young
2006-06-08 15:27 ` Toby Cubitt
2006-06-08 18:05 ` Richard Fish
2006-06-09 11:50 ` Vladimir G. Ivanovic
2006-06-09 19:43 ` Richard Fish
2006-06-16 17:25 ` Thomas T. Veldhouse
2006-06-16 17:50 ` Bob Young
2006-06-16 17:17 ` Thomas T. Veldhouse
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=FAEEIJPAOFEMBBLKPMJEEEJIGDAA.BYoung@NuCORETech.com \
--to=byoung@nucoretech.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