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.54) id 1F25BE-0007Zk-17 for garchives@archives.gentoo.org; Thu, 26 Jan 2006 11:20:44 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.5/8.13.5) with SMTP id k0QBJVFw008306; Thu, 26 Jan 2006 11:19:31 GMT Received: from smtp50.wxs.nl (smtp50-real.wxs.nl [195.121.247.15]) by robin.gentoo.org (8.13.5/8.13.5) with ESMTP id k0QBH7ta019420 for ; Thu, 26 Jan 2006 11:17:07 GMT Received: from pavlvs2.devrieze.net (ip5457f303.direct-adsl.nl [84.87.243.3]) by smtp50.wxs.nl (8.12.10/8.12.10) with ESMTP id k0QBH71f016458 for ; Thu, 26 Jan 2006 12:17:07 +0100 Received: from hex.local.devrieze.net (hex.local.devrieze.net [192.168.1.7]) by pavlvs2.devrieze.net (Postfix) with ESMTP id 39C2110046 for ; Thu, 26 Jan 2006 12:17:07 +0100 (CET) From: Paul de Vrieze To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Re: bootstrapping since gcc 3.4 is stable Date: Thu, 26 Jan 2006 12:17:00 +0100 User-Agent: KMail/1.9 References: <200601252251.k0PMpKZZ004307@gw.open-hosting.net> In-Reply-To: X-Face: #Lb+'V@sGJ;ptgo5}V"W+5OCoo{LZv;bh,s,`WKLi/J)ed1_$0;6X<=?utf-8?q?700LVV/=3BLqPhiDP=5E=0A=09=27f=5Dfnv?=@%6M8\'HR1t=aFx;ePfp{ZQoBe+e)JOQ8T5*(_;mHY+cltLGq<;@$Y,=?utf-8?q?O=5C=24=0A=09Tm=23G6M?=,g![Q62J{na*S9d;R[^8pc%u\aiLqU@`kJtYl"^6pxdW Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2508357.7ChEP8y7fI"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200601261217.06964.pauldv@gentoo.org> X-Archives-Salt: dc79041f-2af9-45c8-9ef1-ca879cf8df1a X-Archives-Hash: 5d79be685180eb6f34fec386727dfa26 --nextPart2508357.7ChEP8y7fI Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Thursday 26 January 2006 03:40, Sven K=F6hler wrote: > >> Seems like a bit ranting to me. Why do you use unsupported installation > >> method if you want it simple? > > > > I don't know about Sven, but the reasons I prefer the "unsupported" > > installation method is all outlined here: > > I have no clue, what "bootstrap.sh" is for anymore. > For me, Installing gentoo was always like this: Ok, let me remind all. Stage 1 is a minimal system that is mainly built=20 statically with the sole purpose of being suitable to build a working syste= m=20 from. It contains a cripled compiler as one of the first things it does is= =20 make a proper one. After that the original compiler should be gone. While=20 some recompiling is needed because of circular dependencies between libc an= d=20 gcc, this should be no issue. After the bootstrap has been run, one should= =20 have a proper minimal building environment that should be able to build all= =20 packages (except for some assumptions on available tools). This minimal=20 environment is called stage 2. Stage 2 should not contain any trace of the bootstrap compiler. If the=20 bootstrap compiler was a 3.3.x version and the final one a 3.4.x version,=20 there should be no 3.3.x version remaining. Be aware though that if the=20 profile does not offer a 3.4 compiler the final will be a 3.3 compiler. If= =20 desired the profile should be changed before running bootstrap.sh Because many ebuilds make assumptions about the environment, and because a= =20 stage 2 will not boot by itself, a number of utilities deemed essential mus= t=20 be installed. Those are part of system. The main ingredient being baselayou= t=20 with it's dependencies. Baselayout is what takes care of booting your syste= m=20 into a working order. > Mike is telling me, that the 2006.0 tarballs will contain gcc-3.4. > Then he's telling me, that the problem, that Im trying to point out, is > going to vanish with the release of the 2006.0 tarballs. Well, yes, > until the next gcc-slot becomes stable. So the problem is not fixed, > just moved to the future again. If a stage1 install does not remove a 3.3.x bootstrap compiler when a 3.4 i= s=20 used as the main, that is a bug in the bootstrap script. As such it should = be=20 fixed. Stage 3 installs just dump a fully functional system, so as such one= =20 should then just take the steps from the handbook that make it bootable.=20 After that the gcc-upgrade guide can be followed, except that world update = is=20 not really needed, and that world normally also includes system such that=20 emerge -e system && emerge -e world is extraneous. > Pretty much work for a beginnner! > And there's pretty much of experience needed. It's easier than going from stage 1. It is possible to skip all the unneede= d=20 compiling, but it's easy to fuck up, and very hard to explain. That's why=20 stage 1 is discouraged. > Actually, the moment when there's an upgrade to glibc and gcc, than > there's no advantage in taking a stage3 - the whole "upgrading the > stage3"-thing will take as long as using a stage1. > Why? because i have to upgrade glibc and gcc - and that is basically > what bootstrap.sh does too. Not really, bootstrap.sh does things in a specific order to take care of=20 cyclic dependencies that fail because stage1 is a minimal ( say crippled )= =20 environment. But indeed you're better off with a stage3 that is based on a= =20 current glibc and gcc version. Minor version numbers don't matter much=20 though. Paul =2D-=20 Paul de Vrieze Gentoo Developer Mail: pauldv@gentoo.org Homepage: http://www.devrieze.net --nextPart2508357.7ChEP8y7fI Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2-ecc0.1.6 (GNU/Linux) iD8DBQBD2K+ybKx5DBjWFdsRAgTEAJ9QonB/I3Lxu/XpYv91eaQqhAMN3QCfUsvt b0fiMUhPbPNnnp8frnzwdXA= =wefp -----END PGP SIGNATURE----- --nextPart2508357.7ChEP8y7fI-- -- gentoo-dev@gentoo.org mailing list