Re: [gentoo-user] Re: default stage3
On Tue, 22 Nov 2005 00:28:26 +0100, Matthias Langer wrote: As I understand it, the first time you recompile new toolchain with your old toolchain, and then the 2nd time you're recompiling the toolchain with the new toolchain, with the idea that the new toolchain will compile/assemble/link/etc everything in a different way than the old toolchain. Please correct if I'm wrong. I would suggest 'emerge -uD gcc emerge -e world'; This should recompile the new toolchain with the new toolchain and be considerably faster. The first command won't do anything, -D doesn't take account of of USE or CFLAG changes. emerge -e system emerge -e world might be better, but there are scripts on the forums that recompile just what you need, in the best order, such as; http://forums.gentoo.org/viewtopic-t-282474.html -- Neil Bothwick I came, I saw, I had no idea what was going on, I left. signature.asc Description: PGP signature
Re: [gentoo-user] Re: default stage3
On 11/22/05, Neil Bothwick [EMAIL PROTECTED] wrote: The first command won't do anything, -D doesn't take account of of USE or CFLAG changes. It will update gcc or any dependancies of gcc to the current version. Unless one of those things have been updated, there is no need to build anything more than once, because the code produced by gcc doesn't change based on the CFLAGS/CHOST/USE settings that _gcc_ was compiled with. emerge -uD system emerge -e world is sufficient. -Richard -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Re: default stage3
On Tue, 2005-11-22 at 09:17 +, Neil Bothwick wrote: On Tue, 22 Nov 2005 00:28:26 +0100, Matthias Langer wrote: As I understand it, the first time you recompile new toolchain with your old toolchain, and then the 2nd time you're recompiling the toolchain with the new toolchain, with the idea that the new toolchain will compile/assemble/link/etc everything in a different way than the old toolchain. Please correct if I'm wrong. I would suggest 'emerge -uD gcc emerge -e world'; This should recompile the new toolchain with the new toolchain and be considerably faster. The first command won't do anything, -D doesn't take account of of USE or CFLAG changes. Well, you are right, in theory; In practice, where the toolchain on the live-cd is not up to date, it will get completley recompiled by emerge -uD gcc (after syncing) - at least I think so ... However, thanks for pointing that out ... emerge -e system emerge -e world might be better, but there are scripts on the forums that recompile just what you need, in the best order, such as; http://forums.gentoo.org/viewtopic-t-282474.html Matthias -- gentoo-user@gentoo.org mailing list
[gentoo-user] Re: default stage3
At Mon, 21 Nov 2005 14:13:14 +0100 Hemmann, Volker Armin [EMAIL PROTECTED] wrote: On Monday 21 November 2005 13:33, Steve B wrote: WTF.. I'm getting ready to rebuild my gentoo box. I have always did a stage 1 install. i was under the impression that if u used a stage 3 u couldn't muck with your CFLAGS or what not. We have a lot in common in this regard. I also always had done stage1 installs. I also misremembered that CFLAGS couldn't be changed if using stage3. I also posted this mis-remembrance to the present list. As was very politely explained to me: 1. It was CHOST, not CFLAGS. 2. You can (at least now, not sure about previously) actually change CHOST, but must run a utility afterward. 3. If you fiddle with USE flags, /etc/package.* files, etc, you can get the effect of a customized stage1 install by recompiling everything twice. I suspect simply emerge -e world; emerge -e world 3A. Only a few items really need to be compiled the first time. 3B. There are scripts in the forums to do this automatically. Thus, I conclude that, unless you are changing bootstrap.sh (which I never did), you really can get the effect of a stage1 starting with stage3. I would not use the term faster to describe the stage3 equivalent of stage1, especially if you are lazy and do the double emerge -e world. Instead, I would say that there are two advantages to the user 1. You can use your machine for reading/sending mail, browsing the web, etc while all the compilation is proceeding. So the machine is usable sooner, even if the procedure is not faster. 2. You avoid the chance to make the kind of error I did in changed USE flags too aggressively, *too early* in the process. Perhaps more important is that there is one big advantage to the developers and seasoned gentoo experts on this list. 1. Fewer installation errors due to faulty understanding of a stage1 process results in fewer requests for help, requests that likely to the expert seem to all be essentially the same, and do not lead to improvement of the stage1 process. A converted supported of stage3 -- stage1-equivalent installs, allan -- gentoo-user@gentoo.org mailing list
RE: [gentoo-user] Re: default stage3
-Original Message- From: Allan Gottlieb [mailto:[EMAIL PROTECTED] Sent: Monday, November 21, 2005 12:16 PM To: gentoo-user@lists.gentoo.org Subject: [gentoo-user] Re: default stage3 At Mon, 21 Nov 2005 14:13:14 +0100 Hemmann, Volker Armin [EMAIL PROTECTED] wrote: On Monday 21 November 2005 13:33, Steve B wrote: WTF.. I'm getting ready to rebuild my gentoo box. I have always did a stage 1 install. i was under the impression that if u used a stage 3 u couldn't muck with your CFLAGS or what not. 3. If you fiddle with USE flags, /etc/package.* files, etc, you can get the effect of a customized stage1 install by recompiling everything twice. I suspect simply emerge -e world; emerge -e world 3A. Only a few items really need to be compiled the first time. 3B. There are scripts in the forums to do this automatically. I installed gentoo on a dual Opteron box this weekend, I've always done stage1 installs, but this time decided to try the recommeded stage3 method. I understand the concept of doing an emerge -e world in order to get the optimization of a stage1 install, and I've done this ( one time ) on the install I just completed. Can sombody explain why it's necessary/desirable to do this *twice*? What real difference does the second execution really make? Thanks, Bob Young -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Re: default stage3
I installed gentoo on a dual Opteron box this weekend, I've always done stage1 installs, but this time decided to try the recommeded stage3 method. I understand the concept of doing an emerge -e world in order to get the optimization of a stage1 install, and I've done this ( one time ) on the install I just completed. Can sombody explain why it's necessary/desirable to do this *twice*? What real difference does the second execution really make? As I understand it, the first time you recompile new toolchain with your old toolchain, and then the 2nd time you're recompiling the toolchain with the new toolchain, with the idea that the new toolchain will compile/assemble/link/etc everything in a different way than the old toolchain. Please correct if I'm wrong. -- Ryan W Sims () ascii ribbon /\ campaign - against html mail - against proprietary attachments -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Re: default stage3
On Mon, 2005-11-21 at 17:01 -0500, Ryan Sims wrote: I installed gentoo on a dual Opteron box this weekend, I've always done stage1 installs, but this time decided to try the recommeded stage3 method. I understand the concept of doing an emerge -e world in order to get the optimization of a stage1 install, and I've done this ( one time ) on the install I just completed. Can sombody explain why it's necessary/desirable to do this *twice*? What real difference does the second execution really make? As I understand it, the first time you recompile new toolchain with your old toolchain, and then the 2nd time you're recompiling the toolchain with the new toolchain, with the idea that the new toolchain will compile/assemble/link/etc everything in a different way than the old toolchain. Please correct if I'm wrong. I would suggest 'emerge -uD gcc emerge -e world'; This should recompile the new toolchain with the new toolchain and be considerably faster. Matthias -- gentoo-user@gentoo.org mailing list
