From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1GNUPB-0008DV-KE for garchives@archives.gentoo.org; Wed, 13 Sep 2006 13:03:54 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.8/8.13.6) with SMTP id k8DD3Aia011939; Wed, 13 Sep 2006 13:03:10 GMT Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.189]) by robin.gentoo.org (8.13.8/8.13.6) with ESMTP id k8DCwjk4002655 for ; Wed, 13 Sep 2006 12:58:46 GMT Received: by nf-out-0910.google.com with SMTP id p46so2140853nfa for ; Wed, 13 Sep 2006 05:58:46 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=MrFYJoe8Fa4DjhWfOeCWxo5OlE4OyT95i7wOooCoJKMrRljuZmUF6PvAwK17ybF7yLAVoXrOoHrtRHtFyohnyai35ZAWLaqZrChOjpbYfezIh6jJ+lds1bXU5As+zKmAT5m9xJohO9CwEzAQFlrQIl8a/coXd7Z5bAE9gm1dlDQ= Received: by 10.48.210.16 with SMTP id i16mr10865048nfg; Wed, 13 Sep 2006 05:58:45 -0700 (PDT) Received: by 10.49.14.9 with HTTP; Wed, 13 Sep 2006 05:58:45 -0700 (PDT) Message-ID: <342e1090609130558v755a8f3djec15482abc904fc8@mail.gmail.com> Date: Wed, 13 Sep 2006 09:58:45 -0300 From: "Daniel da Veiga" To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] changing CHOST In-Reply-To: <17CD9CE4C0FA574A8B29EF02D49B385D2A928D@srvexch-01.mcaschool.local> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <7573e9640609130056y21a925c3i3fd3209da1fadeb5@mail.gmail.com> <17CD9CE4C0FA574A8B29EF02D49B385D2A928D@srvexch-01.mcaschool.local> X-Archives-Salt: cdcc9b01-557a-4052-ab70-aacd64ab5c5e X-Archives-Hash: 3f42bb7025f59cd9e9f5c67b33697b39 On 9/13/06, Timothy A. Holmes wrote: > > On 9/12/06, Richard Fish wrote: > > > On 9/12/06, darren kirby 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 > [Timothy A. Holmes] > > > Hi folks -- I really appreciate all the input on this -- > > It turns out - the system borked and wouldn't let me login from ssh or > console, so I dropped in a live cd and am in the process of rebuilding > it (with the proper stage) > > Thanks again for all the help -- I really appreciate it and I have > learned a great deal > The thread is kinda dead now that the OP borked the system and is reinstalling, but anyway, I'll report to it for future reference. Old threads in this list and foruns talk about this with different ways/advices, but what ended up working for me (changind from i386 to i686) was: some quickpkg's (gcc, glibc, python, portage, libstdc++) (just to be sure I would NOT need a livecd) edit make.conf emerge gcc (as it compiles itself with the new compiler, ended up with i686-pc-linux-gnu) emerge glibc python portage libstdc++ (just to make sure all tools for emerge were already compiled with the new GCC, I don't know wich order the emerge -e system uses for packages, it upgraded my glibc, wich was the whole point of the chost change) emerge -e system (just to make sure most tools were already compiled with the new chost before any reboot/retry) emerge -e world (I guess recompiling stuff with the new chost will take advantage of features present in new processors, that's the whole point of HAVING this flag, isnt? Anyway, its more like a "bug hunting" command, also, broken dynamic linking that could be hanging will appear, specially libstdc++, but I kinda ask myself if it was indeed needed.) Up and running here... -- Daniel da Veiga Computer Operator - RS - Brazil -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GCM/IT/P/O d-? s:- a? C++$ UBLA++ P+ L++ E--- W+++$ N o+ K- w O M- V- PS PE Y PGP- t+ 5 X+++ R+* tv b+ DI+++ D+ G+ e h+ r+ y++ ------END GEEK CODE BLOCK------ -- gentoo-user@gentoo.org mailing list