/[gentoo]/xml/htdocs/doc/en/change-chost.xml
Gentoo

Diff of /xml/htdocs/doc/en/change-chost.xml

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

Revision 1.6 Revision 1.7
1<?xml version="1.0" encoding="UTF-8"?> 1<?xml version="1.0" encoding="UTF-8"?>
2<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> 2<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
3<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/change-chost.xml,v 1.6 2011/09/04 17:53:40 swift Exp $ --> 3<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/change-chost.xml,v 1.7 2012/07/24 12:12:51 swift Exp $ -->
4 4
5<guide lang="en"> 5<guide lang="en">
6 6
7<title>Changing the CHOST variable</title> 7<title>Changing the CHOST variable</title>
8 8
9<author title="Author"> 9<author title="Author">
10 <mail link="amne@gentoo.org">Wernfried Haas</mail> 10 <mail link="amne@gentoo.org">Wernfried Haas</mail>
11</author> 11</author>
12<author title="Reviewer"> 12<author title="Reviewer">
13 <mail link="vapier@gentoo.org">Mike Frysinger</mail> 13 <mail link="vapier@gentoo.org">Mike Frysinger</mail>
14</author> 14</author>
15<author title="Editor"> 15<author title="Editor">
16 <mail link="chriswhite@gentoo.org">Chris White</mail> 16 <mail link="chriswhite@gentoo.org">Chris White</mail>
17</author> 17</author>
18 18
19<abstract> 19<abstract>
20This document explains how to change the CHOST variable of an existing system. 20This document explains how to change the CHOST variable of an existing system.
21</abstract> 21</abstract>
22 22
23<!-- The content of this document is licensed under the CC-BY-SA license --> 23<!-- The content of this document is licensed under the CC-BY-SA license -->
24<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> 24<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
25<license/> 25<license/>
26 26
27<version>3</version> 27<version>4</version>
28<date>2008-07-29</date> 28<date>2012-07-24</date>
29 29
30<chapter> 30<chapter>
31<title>Introduction</title> 31<title>Introduction</title>
32<section> 32<section>
33<body> 33<body>
34 34
35<p> 35<p>
36Changing the CHOST is a big issue that can seriously screw up your system - so 36Changing the CHOST is a big issue that can seriously screw up your system - so
37why is there a guide for that it at all? 37why is there a guide for that it at all?
38</p> 38</p>
39 39
40<p> 40<p>
41There are certain situations where changing the CHOST is inevitable, e.g. if 41There are certain situations where changing the CHOST is inevitable, e.g. if
42you want to upgrade to glibc 2.4 which only supports nptl and you find out that 42you want to upgrade to glibc 2.4 which only supports nptl and you find out that
43your CHOST is i386, which makes it impossible to use nptl. In this case, you 43your CHOST is i386, which makes it impossible to use nptl. In this case, you
50changed from i386 to i686, if you do another change, please change the commands 50changed from i386 to i686, if you do another change, please change the commands
51accordingly. 51accordingly.
52</p> 52</p>
53 53
54</body> 54</body>
55</section> 55</section>
56</chapter> 56</chapter>
57 57
58<chapter> 58<chapter>
59<title>Changing the CHOST variable</title> 59<title>Changing the CHOST variable</title>
60<section> 60<section>
61<title>Building the packages</title> 61<title>Building the packages</title>
62<body> 62<body>
63 63
64<p> 64<p>
65To start out with the CHOST change, edit the <path>/etc/make.conf</path> file 65To start out with the CHOST change, edit the <path>/etc/portage/make.conf</path> file
66and change <b>CHOST</b> value to suit your needs. Then, rebuild the following 66and change <b>CHOST</b> value to suit your needs. Then, rebuild the following
67packages in this order: 67packages in this order:
68</p> 68</p>
69 69
70<pre caption="Rebuilding important system tools"> 70<pre caption="Rebuilding important system tools">
71# <i>emerge -av1 binutils gcc glibc</i> 71# <i>emerge -av1 binutils gcc glibc</i>
72</pre> 72</pre>
73 73
74<impo> 74<impo>
75Please be aware that major gcc upgrades at the same time as changing CHOST 75Please be aware that major gcc upgrades at the same time as changing CHOST
76(e.g. starting with gcc 3.3, CHOST i386 and switching to gcc 4.1, CHOST i686) 76(e.g. starting with gcc 3.3, CHOST i386 and switching to gcc 4.1, CHOST i686)
77can lead to severe side effects. While it may not be impossible to do so, it is 77can lead to severe side effects. While it may not be impossible to do so, it is
78hard to predict which potential problems may arise and document them in this 78hard to predict which potential problems may arise and document them in this
79guide. As a consequence, please do one thing at a time, e.g. upgrade gcc first 79guide. As a consequence, please do one thing at a time, e.g. upgrade gcc first
80according to our <uri link="/doc/en/gcc-upgrading.xml">gcc upgrade guide</uri> 80according to our <uri link="/doc/en/gcc-upgrading.xml">gcc upgrade guide</uri>

Legend:
Removed from v.1.6  
changed lines
  Added in v.1.7

  ViewVC Help
Powered by ViewVC 1.1.20