From: "Bob Young" <BYoung@nucoretech.com>
To: <gentoo-user@lists.gentoo.org>
Subject: RE: [gentoo-user] gcc-4.1.1
Date: Thu, 8 Jun 2006 07:00:22 -0700 [thread overview]
Message-ID: <FAEEIJPAOFEMBBLKPMJEOEHAGCAA.BYoung@NuCORETech.com> (raw)
In-Reply-To: <20060608153131.5653b6b7.hilse@web.de>
> -----Original Message-----
> From: Hans-Werner Hilse [mailto:hilse@web.de]
> Sent: Thursday, June 08, 2006 6:32 AM
> To: gentoo-user@lists.gentoo.org
> Subject: Re: [gentoo-user] gcc-4.1.1
>
> You haven't understood a word from the posting you're replying to.
>
> > It does have to be emerged twice in order for it to be built with
> > itself, anybody who thinks otherwise doesn't understand the basic
> > principles of compiling and linking.
>
> Try to understand what you are replying to. GCC's internal build logic
> does the staging. That's got nothing to do with what your system calls
> when you issue "gcc", and only at that point the slotting of GCC
> versions comes into play.
Show me some documentation for this "staging" you refer to. When you "emerge
gcc" it is built with the current compiler, if the current compiler is gcc
3.4.6, and you emerge gcc 4.1.1, that means that while gcc 4.1.1 is being
emerged it is built with gcc 3.4.6. gcc 4.1.1 can't be built with 4.1.1
because it hasn't been emerged yet, and as far as the system knows it
doesn't actually exist yet. Can you clearly and concisely explain to me how
something that is in the process of being emerged can be used to emerge
itself? Doesn't make sense.
Regards,
Bob Young
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-06-08 14:13 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
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 [this message]
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=FAEEIJPAOFEMBBLKPMJEOEHAGCAA.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