From: "Richard Fish" <bigfish@asmallpond.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] changing CHOST
Date: Wed, 13 Sep 2006 00:56:39 -0700 [thread overview]
Message-ID: <7573e9640609130056y21a925c3i3fd3209da1fadeb5@mail.gmail.com> (raw)
In-Reply-To: <7573e9640609122003l2cc40626q375387c21b12d7d@mail.gmail.com>
On 9/12/06, Richard Fish <bigfish@asmallpond.org> wrote:
> On 9/12/06, darren kirby <bulliver@badcomputer.org> wrote:
> > system. The cpu instructions are forward (but not backward) compatible. Thus,
> > I did not think it necessary for a wholesale rebuild of the entire system on
> > the spot. Indeed it seems this is not as simple as I thought. I may have been
> > thinking changing CHOST was as simple as changing -march or -mcpu...
>
> Well I've brought up the issue on -dev, and it seems that something
> official is in the works on this, so we'll see what comes of that.
> Maybe your answer will turn out to be correct!
And indeed, the emerge -e world may in fact be optional.
A quite from the current draft of the guide [1]:
"""
- You may want to run
# emerge -e world
now. In theory it should not be necessary to do so, but it can not be
100% guaranteed that this is actually the case. ;-)
"""
I think I'd still like to see people run an emerge -e system
regardless...just as an extra safety step to make sure the system
packages are sane. But my understanding of what can be affected by a
change in CHOST is definitely changed.
-Richard
[1] http://dev.gentoo.org/~amne/temp/change-chost.txt
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-09-13 8:03 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-08 0:31 [gentoo-user] Why you use Gentoo Chris White
2006-09-08 0:48 ` John J. Foster
2006-09-08 1:06 ` Lord Sauron
2006-09-08 1:40 ` Statux
2006-09-08 3:31 ` Iain Buchanan
2006-09-08 13:55 ` Mikko Ruuska
2006-09-08 15:05 ` Shawn Singh
2006-09-08 13:16 ` Rafael Barrera Oro
2006-09-08 16:31 ` michael
2006-09-08 22:03 ` Mike Myers
2006-09-08 22:18 ` Richard Fish
2006-09-08 2:47 ` Zac Slade
2006-09-08 11:46 ` Timothy A. Holmes
2006-09-08 23:33 ` Colleen Beamer
2006-09-09 0:33 ` John J. Foster
2006-09-11 8:58 ` Alan McKinnon
2006-09-09 0:48 ` Bob Young
2006-09-09 1:09 ` [gentoo-user] Re: [gentoo-dev] " David Grant
2006-09-09 3:17 ` b.n.
2006-09-09 1:38 ` Dale
2006-09-09 1:59 ` [gentoo-user] " darren kirby
2006-09-09 2:09 ` Dale
2006-09-09 4:26 ` b.n.
2006-09-09 2:51 ` darren kirby
2006-09-09 16:54 ` [gentoo-user] changing CHOST Timothy A. Holmes
2006-09-09 17:04 ` Bo Ørsted Andresen
2006-09-09 17:09 ` darren kirby
2006-09-10 0:34 ` Richard Fish
2006-09-10 1:12 ` John J. Foster
2006-09-10 14:17 ` Timothy A. Holmes
2006-09-10 16:39 ` Jean-Marc Beaune
2006-09-10 17:01 ` Meino Christian Cramer
[not found] ` <7573e9640609101130l5b8073ddr747af67dc363364b@mail.gmail.com>
2006-09-10 22:20 ` Timothy A. Holmes
2006-09-13 2:48 ` darren kirby
[not found] ` <7573e9640609122003l2cc40626q375387c21b12d7d@mail.gmail.com>
2006-09-13 7:56 ` Richard Fish [this message]
2006-09-13 12:34 ` Timothy A. Holmes
2006-09-13 12:58 ` Daniel da Veiga
2006-09-13 7:39 ` Nagatoro
2006-09-09 3:03 ` [gentoo-user] Re: [user] Why you use Gentoo reader
2006-09-09 12:49 ` [gentoo-user] " Rodrigo Lazo
2006-09-10 3:10 ` Zac Slade
2006-09-11 15:35 ` Kevin O'Gorman
-- strict thread matches above, loose matches on Subject: below --
2007-09-23 0:13 [gentoo-user] Changing CHOST David Relson
2007-09-23 1:43 ` Bo Ørsted Andresen
2007-09-23 1:54 ` Albert Hopkins
2007-09-23 1:55 ` Albert Hopkins
2007-09-23 12:47 ` Volker Armin Hemmann
2007-09-23 15:33 ` Doug Whitesell
2007-09-23 16:59 ` Marc Redmann
2007-09-23 21:53 ` Volker Armin Hemmann
2007-09-23 15:37 ` Doug Whitesell
2007-09-24 2:16 ` Mark Shields
2007-09-24 2:38 ` David Relson
2007-09-24 13:29 ` Neil Bothwick
2007-09-24 16:17 ` Florian Philipp
2007-09-25 0:03 ` David Relson
2007-09-25 1:51 ` Doug Whitesell
2007-09-25 6:56 ` Daniel Barkalow
2007-09-25 17:08 ` Florian Philipp
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=7573e9640609130056y21a925c3i3fd3209da1fadeb5@mail.gmail.com \
--to=bigfish@asmallpond.org \
--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