/[gentoo]/xml/htdocs/doc/en/draft/bootstrapping-guide.xml
Gentoo

Diff of /xml/htdocs/doc/en/draft/bootstrapping-guide.xml

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

Revision 1.1 Revision 1.2
1<?xml version='1.0' encoding="UTF-8"?> 1<?xml version='1.0' encoding="UTF-8"?>
2 2
3<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/draft/bootstrapping-guide.xml,v 1.1 2005/11/26 16:23:25 swift Exp $ --> 3<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/draft/bootstrapping-guide.xml,v 1.2 2005/11/30 05:14:15 swift Exp $ -->
4 4
5<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> 5<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
6 6
7<guide link="/doc/en/draft/bootstrapping-guide.xml"> 7<guide link="/doc/en/draft/bootstrapping-guide.xml">
8<title>Gentoo Bootstrapping Guide</title> 8<title>Gentoo Bootstrapping Guide</title>
149<title>Bootstrapping the System</title> 149<title>Bootstrapping the System</title>
150<section> 150<section>
151<title>Installing Gentoo</title> 151<title>Installing Gentoo</title>
152<body> 152<body>
153 153
154<p>
155With the bootable environment at your disposal, you can now boot the target
156system into a small Linux environment. Once booted, follow the installation
157instructions inside the <uri link="/doc/en/handbook">Gentoo Handbook</uri> to
158the point where you chroot into your Gentoo environment. Of course, since you
159only have a stage1 tarball at your disposal, you should use that one instead of
160the stage3 used in the installation instructions.
161</p>
162
163<p>
164After chrooting the system, you should update the Portage tree.
165</p>
166
167<pre caption="Updating the Portage tree">
168# <i>emerge --sync</i>
169</pre>
170
154</body> 171</body>
155</section> 172</section>
156<section> 173<section>
157<title>Using the Bootstrap Script</title> 174<title>Using the Bootstrap Script</title>
158<body> 175<body>
159 176
177<p>
178Next, we'll rebuild the toolchain provided by the stage1 tarball natively.
179Gentoo provides a script that does this for you.
180</p>
181
182<pre caption="Rebuilding the toolchain">
183# <i>/usr/portage/scripts/bootstrap.sh</i>
184</pre>
185
160</body> 186</body>
161</section> 187</section>
162<section> 188<section>
163<title>Building the Core System</title> 189<title>Building the Core System</title>
164<body> 190<body>
165 191
192<p>
193With the toolchain rebuild and ready for general usage, we'll build the core
194system packages for the system:
195</p>
196
197<pre caption="Building the core system packages">
198# <i>emerge --emptytree system</i>
199</pre>
200
166</body> 201</body>
167</section> 202</section>
168<section> 203<section>
169<title>Finishing the Installation</title> 204<title>Finishing the Installation</title>
170<body> 205<body>
206
207<p>
208Now that the core system packages are built, you can continue using the
209installation instructions in the Gentoo Handbook. You will probably get a few
210complaints by Portage telling you certain packages are masked. This is because
211your architecture isn't supported by Gentoo yet, in which case you need to
212unmask the packages in <path>/etc/portage/package.keywords</path> like you did
213previously.
214</p>
171 215
172</body> 216</body>
173</section> 217</section>
174</chapter> 218</chapter>
175 219
180 Should I bootstrap when I want my entire system to use changed CFLAGS, 224 Should I bootstrap when I want my entire system to use changed CFLAGS,
181 CXXFLAGS, USE settings and profile changes? 225 CXXFLAGS, USE settings and profile changes?
182</title> 226</title>
183<body> 227<body>
184 228
229<p>
230No. After your changes, you should rebuild the toolchain first, after which you
231can rebuild the entire system using the new toolchain. When your system suffers
232from circular dependencies, you'll need to rebuild the participants in that
233circle. For instance, if <c>openssl</c> depends on <c>python</c> which depends
234on <c>perl</c> which depends on <c>openssl</c> again (yes, this is a fictuous
235example), rebuild all those packages too.
236</p>
237
238<pre caption="Rebuilding the system">
239# <i>emerge --oneshot --emptytree glibc binutils glibc</i>
240# <i>emerge --emptytree world</i>
241</pre>
242
243<p>
244You don't need to bootstrap here because your architecture still remains the
245same, as is the target system.
246</p>
247
185</body> 248</body>
186</section> 249</section>
187<section> 250<section>
188<title> 251<title>
189 Should I bootstrap when I want my entire system to use changed CHOST settings? 252 Should I bootstrap when I want my entire system to use changed CHOST settings?
190</title> 253</title>
191<body> 254<body>
192 255
256<p>
257Not if the system itself supports the new CHOST setting too (for instance,
258i386-pc-linux-gnu and i686-pc-linux-gnu on a Pentium IV system). Otherwise, yes,
259but then we are really interested in hearing how you managed to install Gentoo
260using the current - wrong - CHOST settings in the first place ;)
261</p>
262
263<p>
264If your system supports both CHOST settings, you can follow the same
265instructions as given in the previous FAQ.
266</p>
267
193</body> 268</body>
194</section> 269</section>
195</chapter> 270</chapter>
196 271
197</guide> 272</guide>

Legend:
Removed from v.1.1  
changed lines
  Added in v.1.2

  ViewVC Help
Powered by ViewVC 1.1.20