> -----Original Message----- > From: Hans-Werner Hilse [mailto:[EMAIL PROTECTED] > 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
