swift 05/11/30 05:14:15 Modified: xml/htdocs/doc/en/draft bootstrapping-guide.xml Log: The simple part...
Revision Changes Path 1.2 +76 -1 xml/htdocs/doc/en/draft/bootstrapping-guide.xml file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/draft/bootstrapping-guide.xml?rev=1.2&content-type=text/x-cvsweb-markup&cvsroot=gentoo plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/draft/bootstrapping-guide.xml?rev=1.2&content-type=text/plain&cvsroot=gentoo diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/draft/bootstrapping-guide.xml.diff?r1=1.1&r2=1.2&cvsroot=gentoo Index: bootstrapping-guide.xml =================================================================== RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/draft/bootstrapping-guide.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- bootstrapping-guide.xml 26 Nov 2005 16:23:25 -0000 1.1 +++ bootstrapping-guide.xml 30 Nov 2005 05:14:15 -0000 1.2 @@ -1,6 +1,6 @@ <?xml version='1.0' encoding="UTF-8"?> -<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/draft/bootstrapping-guide.xml,v 1.1 2005/11/26 16:23:25 swift Exp $ --> +<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/draft/bootstrapping-guide.xml,v 1.2 2005/11/30 05:14:15 swift Exp $ --> <!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> @@ -151,24 +151,68 @@ <title>Installing Gentoo</title> <body> +<p> +With the bootable environment at your disposal, you can now boot the target +system into a small Linux environment. Once booted, follow the installation +instructions inside the <uri link="/doc/en/handbook">Gentoo Handbook</uri> to +the point where you chroot into your Gentoo environment. Of course, since you +only have a stage1 tarball at your disposal, you should use that one instead of +the stage3 used in the installation instructions. +</p> + +<p> +After chrooting the system, you should update the Portage tree. +</p> + +<pre caption="Updating the Portage tree"> +# <i>emerge --sync</i> +</pre> + </body> </section> <section> <title>Using the Bootstrap Script</title> <body> +<p> +Next, we'll rebuild the toolchain provided by the stage1 tarball natively. +Gentoo provides a script that does this for you. +</p> + +<pre caption="Rebuilding the toolchain"> +# <i>/usr/portage/scripts/bootstrap.sh</i> +</pre> + </body> </section> <section> <title>Building the Core System</title> <body> +<p> +With the toolchain rebuild and ready for general usage, we'll build the core +system packages for the system: +</p> + +<pre caption="Building the core system packages"> +# <i>emerge --emptytree system</i> +</pre> + </body> </section> <section> <title>Finishing the Installation</title> <body> +<p> +Now that the core system packages are built, you can continue using the +installation instructions in the Gentoo Handbook. You will probably get a few +complaints by Portage telling you certain packages are masked. This is because +your architecture isn't supported by Gentoo yet, in which case you need to +unmask the packages in <path>/etc/portage/package.keywords</path> like you did +previously. +</p> + </body> </section> </chapter> @@ -182,6 +226,25 @@ </title> <body> +<p> +No. After your changes, you should rebuild the toolchain first, after which you +can rebuild the entire system using the new toolchain. When your system suffers +from circular dependencies, you'll need to rebuild the participants in that +circle. For instance, if <c>openssl</c> depends on <c>python</c> which depends +on <c>perl</c> which depends on <c>openssl</c> again (yes, this is a fictuous +example), rebuild all those packages too. +</p> + +<pre caption="Rebuilding the system"> +# <i>emerge --oneshot --emptytree glibc binutils glibc</i> +# <i>emerge --emptytree world</i> +</pre> + +<p> +You don't need to bootstrap here because your architecture still remains the +same, as is the target system. +</p> + </body> </section> <section> @@ -190,6 +253,18 @@ </title> <body> +<p> +Not if the system itself supports the new CHOST setting too (for instance, +i386-pc-linux-gnu and i686-pc-linux-gnu on a Pentium IV system). Otherwise, yes, +but then we are really interested in hearing how you managed to install Gentoo +using the current - wrong - CHOST settings in the first place ;) +</p> + +<p> +If your system supports both CHOST settings, you can follow the same +instructions as given in the previous FAQ. +</p> + </body> </section> </chapter> -- [email protected] mailing list
