Gentoo Archives: gentoo-commits

From: "Fabian Groffen (grobian)" <grobian@g.o>
To: gentoo-commits@l.g.o
Subject: [gentoo-commits] gentoo commit in xml/htdocs/proj/en/gentoo-alt/prefix: bootstrap-linux.xml
Date: Wed, 09 Jan 2008 18:33:18
Message-Id: E1JCfjm-0004OB-Oc@stork.gentoo.org
1 grobian 08/01/09 18:33:14
2
3 Modified: bootstrap-linux.xml
4 Log:
5 Adjust to latest bootstrap image
6
7 Revision Changes Path
8 1.19 xml/htdocs/proj/en/gentoo-alt/prefix/bootstrap-linux.xml
9
10 file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/bootstrap-linux.xml?rev=1.19&view=markup
11 plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/bootstrap-linux.xml?rev=1.19&content-type=text/plain
12 diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/bootstrap-linux.xml?r1=1.18&r2=1.19
13
14 Index: bootstrap-linux.xml
15 ===================================================================
16 RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/bootstrap-linux.xml,v
17 retrieving revision 1.18
18 retrieving revision 1.19
19 diff -u -r1.18 -r1.19
20 --- bootstrap-linux.xml 2 Jan 2008 09:35:57 -0000 1.18
21 +++ bootstrap-linux.xml 9 Jan 2008 18:33:14 -0000 1.19
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-linux.xml,v 1.18 2008/01/02 09:35:57 grobian Exp $ -->
26 +<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/bootstrap-linux.xml,v 1.19 2008/01/09 18:33:14 grobian Exp $ -->
27
28 <guide link="/proj/en/gentoo-alt/prefix/bootstrap-linux.xml" lang="en">
29 <title>Gentoo Prefixed Portage Bootstrap Process for Linux</title>
30 @@ -19,8 +19,8 @@
31 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
32 <license/>
33
34 - <version>1.5</version>
35 - <date>2008-01-02</date>
36 + <version>1.6</version>
37 + <date>2008-01-09</date>
38
39 <chapter>
40 <title>Bootstrapping on Linux</title>
41 @@ -119,15 +119,7 @@
42 for a successful bootstrap:
43 </p>
44 <pre caption="Setup ld directions">
45 -$ <i>export LDFLAGS="\
46 - -L${EPREFIX}/usr/lib64 \
47 - -Wl,-rpath=${EPREFIX}/usr/lib64 \
48 - -L${EPREFIX}/usr/lib \
49 - -Wl,-rpath=${EPREFIX}/usr/lib \
50 - -L${EPREFIX}/lib64 \
51 - -Wl,-rpath=${EPREFIX}/lib64 \
52 - -L${EPREFIX}/lib \
53 - -Wl,-rpath=${EPREFIX}/lib"</i>
54 +$ <i>export LDFLAGS="-L${EPREFIX}/usr/lib -Wl,-rpath=${EPREFIX}/usr/lib -L${EPREFIX}/lib -Wl,-rpath=${EPREFIX}/lib"</i>
55 $ <i>export CPPFLAGS="-I${EPREFIX}/usr/include"</i>
56 </pre>
57 <p>
58 @@ -164,7 +156,7 @@
59 </p>
60 <pre caption="emerge autotools">
61 $ <i>emerge --oneshot --nodeps "=autoconf-2.6*" "autoconf-wrapper"</i>
62 -$ <i>emerge --oneshot --nodeps texinfo</i>
63 +$ <i>emerge --oneshot --nodeps help2man texinfo</i>
64 $ <i>emerge --oneshot --nodeps "m4"</i>
65 $ <i>emerge --oneshot --nodeps "=autoconf-2.1*" "=autoconf-2.6*"</i>
66 $ <i>emerge --oneshot --nodeps "=automake-1.4*" "=automake-1.5*" "=automake-1.6*" "=automake-1.7*" "=automake-1.8*" "=automake-1.9*" "=automake-1.10*" "automake-wrapper"</i>
67 @@ -193,6 +185,7 @@
68 $ <i>emerge --oneshot --nodeps python</i>
69 $ <i>emerge --oneshot --nodeps findutils</i>
70 $ <i>emerge --oneshot --nodeps tar</i>
71 +$ <i>emerge --oneshot gawk</i>
72 </pre>
73 <note>If you feel above tools are up-to-date enough on your
74 system, you may try skipping their installation here.</note>
75 @@ -208,13 +201,6 @@
76 $ <i>env FEATURES="-collision-protect" emerge --oneshot --nodeps portage</i>
77 </pre>
78 <p>
79 - Next, we get GNU <c>awk</c>, as most ebuilds expect this
80 - <c>awk</c> when they use it.
81 - </p>
82 - <pre caption="emerge gawk">
83 -$ <i>emerge --oneshot gawk</i>
84 - </pre>
85 - <p>
86 Some, if not many, scripts and tools within a Gentoo system
87 assume the availability of the <c>baselayout</c> package. We
88 make sure here we have it, for this reason. In fact, it would
89 @@ -247,13 +233,6 @@
90 failures due to dependencies.
91 </p>
92 <p>
93 - Since we have some basic stuff now, we might want the benefit
94 - of an updated tree. To use it, emerge <c>subversion</c>:
95 - </p>
96 - <pre caption="emerge subversion">
97 -$ <i>emerge subversion</i>
98 - </pre>
99 - <p>
100 We can now update the tree. Since snapshots now are actually
101 (anonymous) SVN checkouts of the tree, we can immediately use
102 SVN commands on the tree instead of checking a tree out first.
103 @@ -267,7 +246,7 @@
104 </pre>
105 <p>
106 To really do this properly, after emerging <c>system</c>, one
107 - should re-emerge <c>world</c>, because now all packages can
108 + should re-emerge <c>system</c>, because now all packages can
109 be compiled with all tools from the prefix, instead of based
110 on tools in the system root. Before you do though, this is
111 the good time to set your general <c>USE</c>-flags, such as
112 @@ -285,20 +264,18 @@
113 <p>
114 Since we're about to rebuild our system for the last time, we
115 can unset all hacks we made to help the bootstrap process.
116 - This time we emerge <c>world</c> to include the packages
117 - necessary for <c>subversion</c>.
118 </p>
119 <pre caption="Unsetting LDFLAGS and CPPFLAGS variables">
120 $ <i>unset LDFLAGS</i>
121 $ <i>unset CPPFLAGS</i>
122 -$ <i>emerge -e system world</i>
123 +$ <i>emerge -e system</i>
124 </pre>
125 <note>
126 tcsh users can use <c>unsetenv LDFLAGS</c> and alike for
127 <c>CPPFLAGS</c>.
128 </note>
129 <p>
130 - After <c>world</c> has emerged successfully, your prefix will
131 + After <c>system</c> has emerged successfully, your prefix will
132 be set up properly, and you can emerge the whichever tools you
133 choose from the prefix tree.
134 </p>
135
136
137
138 --
139 gentoo-commits@l.g.o mailing list