| 1 |
grobian 08/01/09 18:27:45 |
| 2 |
|
| 3 |
Modified: bootstrap-solaris.xml |
| 4 |
Log: |
| 5 |
Adjust to latest bootstrap image |
| 6 |
|
| 7 |
Revision Changes Path |
| 8 |
1.21 xml/htdocs/proj/en/gentoo-alt/prefix/bootstrap-solaris.xml |
| 9 |
|
| 10 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/bootstrap-solaris.xml?rev=1.21&view=markup |
| 11 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/bootstrap-solaris.xml?rev=1.21&content-type=text/plain |
| 12 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/bootstrap-solaris.xml?r1=1.20&r2=1.21 |
| 13 |
|
| 14 |
Index: bootstrap-solaris.xml |
| 15 |
=================================================================== |
| 16 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/bootstrap-solaris.xml,v |
| 17 |
retrieving revision 1.20 |
| 18 |
retrieving revision 1.21 |
| 19 |
diff -u -r1.20 -r1.21 |
| 20 |
--- bootstrap-solaris.xml 22 Dec 2007 22:10:18 -0000 1.20 |
| 21 |
+++ bootstrap-solaris.xml 9 Jan 2008 18:27:45 -0000 1.21 |
| 22 |
@@ -1,6 +1,6 @@ |
| 23 |
<?xml version="1.0" encoding="UTF-8"?> |
| 24 |
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> |
| 25 |
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/bootstrap-solaris.xml,v 1.20 2007/12/22 22:10:18 grobian Exp $ --> |
| 26 |
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/bootstrap-solaris.xml,v 1.21 2008/01/09 18:27:45 grobian Exp $ --> |
| 27 |
|
| 28 |
<guide link="/proj/en/gentoo-alt/prefix/bootstrap-solaris.xml" lang="en"> |
| 29 |
<title>Gentoo Prefixed Portage Bootstrap Process for Solaris</title> |
| 30 |
@@ -19,8 +19,8 @@ |
| 31 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
| 32 |
<license/> |
| 33 |
|
| 34 |
- <version>1.4</version> |
| 35 |
- <date>2007-12-22</date> |
| 36 |
+ <version>1.5</version> |
| 37 |
+ <date>2008-01-09</date> |
| 38 |
|
| 39 |
<chapter> |
| 40 |
<title>Bootstrapping on Solaris 10</title> |
| 41 |
@@ -29,17 +29,18 @@ |
| 42 |
<title>Introduction</title> |
| 43 |
<body> |
| 44 |
<p> |
| 45 |
- Bootstrapping on Solaris 10 is relatively simple, if you |
| 46 |
+ Bootstrapping on Solaris 10 is relatively simple if you |
| 47 |
compare it to its predecessors. It comes with bash3 and a |
| 48 |
gcc-3.4.3 compiler by default, and with the download manager |
| 49 |
wget. If you still are in the process of installing Solaris |
| 50 |
10, make sure you install wget, to make things easier later on. |
| 51 |
</p> |
| 52 |
<p> |
| 53 |
- Solaris is one of the more "Spartan" platforms to bootstrap |
| 54 |
- on, and for sure not as easy as for instance a Linux |
| 55 |
- distribution or Mac OS X. However, don't despair when things |
| 56 |
- go wrong, it's just known to be hard(er), but not impossible. |
| 57 |
+ Though being relatively simple, Solaris is one of the more |
| 58 |
+ "Spartan" platforms to bootstrap on, and for sure not as easy |
| 59 |
+ as for instance a Linux distribution or Mac OS X. However, |
| 60 |
+ don't despair when things go wrong, it's just known to be |
| 61 |
+ hard(er), but not impossible. |
| 62 |
</p> |
| 63 |
</body> |
| 64 |
</section><!-- }}} --> |
| 65 |
@@ -170,7 +171,7 @@ |
| 66 |
$ <i>emerge --oneshot --nodeps sys-apps/baselayout-prefix</i> |
| 67 |
$ <i>emerge --oneshot --nodeps sys-devel/flex</i> |
| 68 |
$ <i>emerge --oneshot --nodeps sys-devel/binutils-config</i> |
| 69 |
-$ <i>emerge --oneshot --nodeps "=sys-devel/binutils-2.16*"</i> |
| 70 |
+$ <i>emerge --oneshot --nodeps sys-devel/binutils</i> |
| 71 |
$ <i>emerge --oneshot --nodeps sys-devel/gcc-config</i> |
| 72 |
$ <i>emerge --oneshot --nodeps sys-devel/gcc</i> |
| 73 |
</pre> |
| 74 |
@@ -234,6 +235,7 @@ |
| 75 |
$ <i>emerge --oneshot --nodeps grep</i> |
| 76 |
$ <i>emerge --oneshot --nodeps make</i> |
| 77 |
$ <i>emerge --oneshot --nodeps bison</i> |
| 78 |
+$ <i>emerge --oneshot gawk</i> |
| 79 |
</pre> |
| 80 |
<p> |
| 81 |
Before we continue to emerge all ebuilds from <c>system</c>, |
| 82 |
@@ -247,13 +249,6 @@ |
| 83 |
$ <i>env FEATURES="-collision-protect" emerge --oneshot --nodeps portage</i> |
| 84 |
</pre> |
| 85 |
<p> |
| 86 |
- Next, we get GNU <c>awk</c>, as most ebuilds expect this |
| 87 |
- <c>awk</c> when they use it. |
| 88 |
- </p> |
| 89 |
- <pre caption="emerge gawk"> |
| 90 |
-$ <i>emerge --oneshot gawk</i> |
| 91 |
- </pre> |
| 92 |
- <p> |
| 93 |
Now we're about to start the big work, we remove the temporary |
| 94 |
directory and its use as we got it all in our prefix now. |
| 95 |
</p> |
| 96 |
@@ -275,13 +270,6 @@ |
| 97 |
failures due to dependencies. |
| 98 |
</p> |
| 99 |
<p> |
| 100 |
- Since we have some basic stuff now, we might want the benefit |
| 101 |
- of an updated tree. To use it, emerge <c>subversion</c>: |
| 102 |
- </p> |
| 103 |
- <pre caption="emerge subversion"> |
| 104 |
-$ <i>emerge subversion</i> |
| 105 |
- </pre> |
| 106 |
- <p> |
| 107 |
We can now update the tree. Since snapshots now are actually |
| 108 |
(anonymous) SVN checkouts of the tree, we can immediately use |
| 109 |
SVN commands on the tree instead of checking a tree out first. |
| 110 |
@@ -295,7 +283,7 @@ |
| 111 |
</pre> |
| 112 |
<p> |
| 113 |
To really do this properly, after emerging <c>system</c>, one |
| 114 |
- should re-emerge <c>world</c>, because now all packages can |
| 115 |
+ should re-emerge <c>system</c>, because now all packages can |
| 116 |
be compiled with all tools from the prefix, instead of based |
| 117 |
on tools in the system root. Before you do though, this is |
| 118 |
the good time to set your general <c>USE</c>-flags, such as |
| 119 |
@@ -313,20 +301,18 @@ |
| 120 |
<p> |
| 121 |
Since we're about to rebuild our system for the last time, we |
| 122 |
can unset all hacks we made to help the bootstrap process. |
| 123 |
- This time we emerge <c>world</c> to include the packages |
| 124 |
- necessary for <c>subversion</c>. |
| 125 |
</p> |
| 126 |
<pre caption="Unsetting LDFLAGS and CPPFLAGS variables"> |
| 127 |
$ <i>unset LDFLAGS</i> |
| 128 |
$ <i>unset CPPFLAGS</i> |
| 129 |
-$ <i>emerge -e system world</i> |
| 130 |
+$ <i>emerge -e system</i> |
| 131 |
</pre> |
| 132 |
<note> |
| 133 |
tcsh users can use <c>unsetenv LDFLAGS</c> and alike for |
| 134 |
<c>CPPFLAGS</c>. |
| 135 |
</note> |
| 136 |
<p> |
| 137 |
- After <c>world</c> has emerged successfully, your prefix will |
| 138 |
+ After <c>system</c> has emerged successfully, your prefix will |
| 139 |
be set up properly, and you can emerge the whichever tools you |
| 140 |
choose from the prefix tree. |
| 141 |
</p> |
| 142 |
|
| 143 |
|
| 144 |
|
| 145 |
-- |
| 146 |
gentoo-commits@l.g.o mailing list |
Archives