public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Allan Gottlieb <gottlieb@nyu.edu>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Is Gentoo still on the right path?
Date: Thu, 17 Nov 2005 08:52:47 -0500	[thread overview]
Message-ID: <yu964qr4c0g.fsf@nyu.edu> (raw)
In-Reply-To: <20051117092346.47fe8d17@krikkit.digimed.co.uk> (Neil Bothwick's message of "Thu, 17 Nov 2005 09:23:46 +0000")

At Thu, 17 Nov 2005 09:23:46 +0000 Neil Bothwick <neil@digimed.co.uk> wrote:

> On Wed, 16 Nov 2005 19:03:18 -0800, Mark Knecht wrote:
>
>>    Would you mind sharing what changes you made to your CFLAGS to get
>> the equivalent of a Stage 1 install?
>
> When installing a stage 3 you are using packages compiled with the
> default compiler and USE flags. All I did was set them up as I wanted and
> rebuilt everything with emerge -e world. The specific change I made in
> this case was changing -mcpu to G4 and adding -fomit-frame-pointer, which
> may be unnecessary. But that's not relevant, the emerge -e world is.

What about -march ?  At one point that was something that you weren't
supposed to change unless using stage1.  If one changes -march after
stage3, are we supposed to first run bootstrap.sh before emerge -e ?

Although I always did stage1 installs, I must confess to once getting
into trouble by changing USE flags "too early".  This taught me the
advantage of first going stage1-->stage2-->stage3 with the std USE
flags and only then changing USE flags.  I realize that in that case
one might as well start with stage3 (assuming you can change -march).

thanks,
allan
-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2005-11-17 14:06 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-16 16:20 [gentoo-user] Is Gentoo still on the right path? Derek Tracy
2005-11-16 18:23 ` Mark Knecht
2005-11-19 15:07   ` A. Khattri
2005-11-16 19:53 ` Daniel da Veiga
2005-11-16 20:50   ` Derek Tracy
2005-11-16 21:50     ` Jeff Smelser
2005-11-16 22:32       ` Derek Tracy
2005-11-17  0:26         ` Richard Fish
2005-11-16 22:46     ` Neil Bothwick
2005-11-17 11:24       ` Derek Tracy
2005-11-17 11:59         ` Nagatoro
2005-11-17  7:44   ` jarmstrong
2005-11-16 22:51     ` Neil Bothwick
2005-11-17  3:03       ` Mark Knecht
2005-11-17  9:23         ` Neil Bothwick
2005-11-17 13:52           ` Allan Gottlieb [this message]
2005-11-17 14:35             ` Neil Bothwick
2005-11-17 17:44               ` Allan Gottlieb
2005-11-17 15:21           ` Mark Knecht
2005-11-17  0:17     ` Ciaran McCreesh
2005-11-17  0:34       ` Richard Fish
2005-11-16 20:12 ` Nick Rout
2005-11-16 20:30   ` kashani
2005-11-16 21:04     ` Nick Rout
2005-11-16 20:30   ` Benjamin Martin
2005-11-16 20:47     ` Mark Knecht
2005-11-16 20:55       ` Benjamin Martin
2005-11-16 20:59         ` Derek Tracy
2005-11-16 21:10         ` Mark Knecht
2005-11-16 21:20           ` Derek Tracy
2005-11-16 22:31             ` Richard Fish
2005-11-16 23:24             ` kashani
2005-11-16 21:33           ` Manuel McLure
2005-11-16 21:53         ` Jeff Smelser
2005-11-16 20:54   ` Zac Medico
2005-11-16 22:22 ` Richard Fish
2005-11-16 22:37   ` Derek Tracy
2005-11-17  0:21     ` Richard Fish
2005-11-17 14:03 ` Bill Roberts
  -- strict thread matches above, loose matches on Subject: below --
2005-11-16 20:27 Budd, Tracy

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=yu964qr4c0g.fsf@nyu.edu \
    --to=gottlieb@nyu.edu \
    --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