[gentoo-commits] gentoo commit in xml/htdocs/proj/en/gentoo-alt/prefix: bootstrap-solaris.xml

[Fabian Groffen (grobian)]

grobian     08/04/19 10:15:07

  Modified:             bootstrap-solaris.xml
  Log:
  Fix Solaris bootstrapping guide, and add directions for a native 64-bits Prefix

Revision  Changes    Path
1.24                 xml/htdocs/proj/en/gentoo-alt/prefix/bootstrap-solaris.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/bootstrap-solaris.xml?rev=1.24&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/bootstrap-solaris.xml?rev=1.24&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/bootstrap-solaris.xml?r1=1.23&r2=1.24

Index: bootstrap-solaris.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/bootstrap-solaris.xml,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -r1.23 -r1.24
--- bootstrap-solaris.xml	18 Mar 2008 21:52:27 -0000	1.23
+++ bootstrap-solaris.xml	19 Apr 2008 10:15:07 -0000	1.24
@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/bootstrap-solaris.xml,v 1.23 2008/03/18 21:52:27 grobian Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/bootstrap-solaris.xml,v 1.24 2008/04/19 10:15:07 grobian Exp $ -->
 
 <guide link="/proj/en/gentoo-alt/prefix/bootstrap-solaris.xml" lang="en">
   <title>Gentoo Prefix Bootstrap Process for Solaris</title>
@@ -19,8 +19,8 @@
   <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
   <license/>
 
-  <version>1.6</version>
-  <date>2008-02-21</date>
+  <version>1.7</version>
+  <date>2008-04-19</date>
 
   <chapter>
     <title>Bootstrapping on Solaris 10</title>
@@ -95,6 +95,13 @@
           <path>/usr/sfw/sparc-sun-solaris2.10/bin</path> instead of
           <path>/usr/sfw/i386-sun-solaris2.10/bin</path></note>
         <p>
+          If you want to end up with a 64-bits native Prefix
+          installation, then set your <c>CHOST</c> variable accordingly
+          to either <c>x86_64-pc-solaris2.10</c> or
+          <c>sparcv9-sun-solaris2.10</c>.  You <e>only</e> need to do
+          this if you want a 64-bits native Prefix!
+        </p>
+        <p>
           Now the path is set, start with downloading the bootstrap
           script from
           <uri>http://overlays.gentoo.org/proj/alt/browser/trunk/prefix-overlay/scripts/bootstrap-prefix.sh?format=txt</uri>.
@@ -115,8 +122,10 @@
 $ <i>./bootstrap-prefix.sh $EPREFIX/tmp gawk</i>
 $ <i>./bootstrap-prefix.sh $EPREFIX portage</i>
         </pre>
-        <note>Please note that <c>wget</c>, <c>sed</c>, etc. are
-          installed in <path>$EPREFIX/tmp</path>!</note>
+        <note>
+          Please note that <c>wget</c>, <c>sed</c>, etc. are installed
+          in <path>$EPREFIX/tmp</path>!
+        </note>
         <p>
           The script will setup the <path>$EPREFIX</path>
           directory, download a portage tree snapshot, unpack it and
@@ -129,6 +138,12 @@
 $ <i>export CPPFLAGS="-I${EPREFIX}/usr/include"</i>
         </pre>
         <p>
+          If you are targetting a 64-bits native Prefix, append
+          <c>-L</c> and <c>-R</c> flags for <c>/usr/sfw/lib/64</c> to
+          your <c>LDFLAGS</c>.  Additionally set <c>CC="gcc -m64"</c>,
+          <c>CXX="g++ -m64"</c> and <c>HOSTCC="gcc -m64"</c>.
+        </p>
+        <p>
           Because we installed some new applications, we will instruct
           bash to reconsider all paths we have:
         </p>
@@ -171,14 +186,28 @@
           Gentoo colour scheme.
         </p>
         <pre caption="emerge linker and compiler">
-$ <i>emerge --oneshot m4</i>
+$ <i>emerge --oneshot "&lt;m4-1.4.11"</i>
 $ <i>emerge --oneshot --nodeps baselayout-prefix</i>
 $ <i>emerge --oneshot --nodeps flex</i>
-$ <i>emerge --oneshot --nodeps binutils-config</i>
+$ <i>emerge --oneshot --nodeps binutils-config</i>  (64-bits: see note!)
 $ <i>emerge --oneshot --nodeps binutils</i>
 $ <i>emerge --oneshot --nodeps gcc-config</i>
 $ <i>emerge --oneshot --nodeps gcc</i>
         </pre>
+        <note>
+          64-bit native Prefix bootstrappers need to workaround an
+          inconvenience with <c>binutils-config</c>.  When emerging this
+          package use <c>env CFLAGS="-O2 -pipe -m64" emerge ...</c>.
+        </note>
+        <p>
+          Since the tools for building are now installed in your Prefix,
+          the little helpers we used before are no longer necessary.
+          They may even cause trouble, so we unset them.
+        </p>
+        <pre caption="unset no longer needed environment variables">
+$ <i>unset LDFLAGS CPPFLAGS CHOST CC CXX HOSTCC</i>
+        </pre>
+        <note>tcsh users can use <c>unsetenv LDFLAGS</c>, etc.</note>
         <p>
           We continue getting more tools in our Prefix.  We no longer
           ignore dependencies, so a lot of packages will be emerged at
@@ -247,28 +276,21 @@
           <c>CFLAGS</c>!  Note that the code below is an example, and is
           meant for inspiration only.
         </p>
-        <pre caption="Customising the Prefix installation - example">
+        <pre caption="customising the Prefix installation - example">
 $ <i>echo 'USE="unicode nls"' >> $EPREFIX/etc/make.conf</i>
 $ <i>echo 'CFLAGS="-O2 -pipe"' >> $EPREFIX/etc/make.conf</i>
 $ <i>echo 'CXXFLAGS="${CFLAGS}"' >> $EPREFIX/etc/make.conf</i>
         </pre>
         <p>
           Since we have everything in place for a self-catered rebuild,
-          we can unset all hacks we made to help the bootstrap process,
-          and start the final stage to install the Prefix system.  This
-          final stage recompiles everything in the system, but now all
-          packages can be compiled with tools from the Prefix, instead
-          of those from the host system.
-        </p>
-        <pre caption="Unsetting LDFLAGS and CPPFLAGS variables">
-$ <i>unset LDFLAGS</i>
-$ <i>unset CPPFLAGS</i>
+          we can start the final stage to install the Prefix system.
+          This final stage recompiles everything in the system, but now
+          all packages can be compiled with tools from the Prefix,
+          instead of those from the host system.
+        </p>
+        <pre caption="doing the final system installation">
 $ <i>emerge -e system</i>
         </pre>
-        <note>
-          tcsh users can use <c>unsetenv LDFLAGS</c> and alike for
-          <c>CPPFLAGS</c>.
-        </note>
         <p>
           After <c>system</c> has emerged successfully, your Prefix will
           be set up properly, and you can emerge the whichever tools you



-- 
gentoo-commits@l.g.o mailing list