Attachment 97342 Details for Bug 147502 – new version

new version

change-chost.xml (text/xml), 8.41 KB, created by Wernfried Haas (RETIRED) on 2006-09-18 08:50:16 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Wernfried Haas (RETIRED)

Created: 2006-09-18 08:50:16 UTC

Size: 8.41 KB

patch

obsolete

><?xml version="1.0" encoding="UTF-8"?>
><!DOCTYPE guide SYSTEM "http://www.gentoo.org/dtd/guide.dtd">
>
>
><guide link="/doc/en/change-chost.xml" lang="en">
><title>Changing the CHOST</title>
>
><author title="Author">
> <mail link="amne@gentoo.org">Wernfried Haas</mail>
></author>
>
><author title="GuideXML">
> <mail link="chriswhite@gentoo.org">Chris White</mail>
></author>
>
><abstract>
>This document explains how to change the CHOST of an existing system. As this
>is a fundamental change to your system and can seriously damage your system,
>it is vital to follow these instructions very closely.
></abstract>
>
>
>
><license/>
>
><version>1.0</version>
><date>2006-09-13</date>
>
><chapter>
><title>Introduction</title>
><section>
><body>
>
>Changing the CHOST is a big issue that can seriously screw up your system - so
>why is there a guide for that it at all?
>
>There are certain situations where changing the CHOST is inevitable, e.g. if
>you want to upgrade to glibc 2.4 which only supports nptl and you find out
>that your CHOST is i386, which makes it impossible to use nptl. In this case,
>you don't have a lot of options, and changing CHOST is one of them.
>
>Even if following these instructions problems may arise, so please make sure
>to read and execute them very carefully. In this example the CHOST will be
>changed from i386 to i686, it is likely you do another change, please
>change the commands accordingly.
>
>
></body>
></section>
></chapter>
>
><chapter>
><title>Changing the CHOST</title>
><section>
><title>Building The Packages</title>
><body>
>
>
>To start out with the CHOST change, edit the file <path>/etc/make.conf</path>
>and change CHOST value to suit your needs. Then, rebuild the following
>packages in this order:
>
>
><pre caption="Rebuilding important system tools">
># emerge -av1 binutils gcc glibc
></pre>
>
></body>
></section>
><section>
><title>Verifying Things Work</title>
><body>
>
>
>Now it is time to make sure that your <c>gcc-config</c>/<c>binutils-config</c>
>settings are sane and you dont have any leftovers left behind in
><path>/etc/env.d/</path>. 
>
>
>
>The output of gcc-config and binutils-config should look like this (may differ
>according to your gcc version and chost, gcc 4.1.1 and i686 here):
>
>
><pre caption="Verifying a sane setup">
># gcc-config -l
> [1] i686-pc-linux-gnu-4.1.1 *
># gcc-config -c
>i686-pc-linux-gnu-4.1.1
>
># binutils-config -l
> [1] i686-pc-linux-gnu-2.16.1 *
># binutils-config -c
>i686-pc-linux-gnu-2.16.1
>
># <comment>(Now take a look around /etc/env.d/)</comment>
># cd /etc/env.d/
></pre>
>
>
>Next, check to see if there are references to the old CHOST:
>
>
>
><pre caption="Checking for old CHOST references.">
># grep 386 *
>05gcc-i386-pc-linux-gnu:PATH="/usr/i386-pc-linux-gnu/gcc-bin/4.1.1"
>05gcc-i386-pc-linux-gnu:ROOTPATH="/usr/i386-pc-linux-gnu/gcc-bin/4.1.1"
></pre>
>
><note>
>This may not happen to you, but in this case 05gcc-i386-pc-linux-gnu contains
>references to the old CHOST. Things may look differently on your system
>depending on which CHOST you are changing to/from, or even be just fine. 
>The name may also be 05gcc-your_new_CHOST-pc-linux-gnu.
></note>
>
>
>Before deleting the file, let's check for files with the updated CHOST:
>
>
><pre caption="Checking for files with the updated CHOST">
># grep 686 * 
>05binutils:MANPATH=/usr/share/binutils-data/i686-pc-linux-gnu/2.16.1/man
>05binutils:INFOPATH=/usr/share/binutils-data/i686-pc-linux-gnu/2.16.1/info
>05binutils:LDPATH=/usr/i686-pc-linux-gnu/lib
>05gcc:PATH="/usr/i686-pc-linux-gnu/gcc-bin/4.1.1"
>05gcc:ROOTPATH="/usr/i686-pc-linux-gnu/gcc-bin/4.1.1"
>05gcc:MANPATH="/usr/share/gcc-data/i686-pc-linux-gnu/4.1.1/man"
>05gcc:INFOPATH="/usr/share/gcc-data/i686-pc-linux-gnu/4.1.1/info"
>05gcc:LDPATH="/usr/lib/gcc/i686-pc-linux-gnu/4.1.1"
></pre>
>
>
>This one looks good as there should always be only one file for <c>gcc</c> in
><path>/etc/env.d/</path> (05gcc in this example), so let's delete the one with the wrong references:
>
>
><pre caption="Removing the files with incorrect references">
># rm 05gcc-i386-pc-linux-gnu
></pre>
>
>
>The same also applies to <c>binutils</c> - if there's an extra one, see which is the
>outdated one and delete it. Next, check your <path>/etc/env.d/binutils/</path>
>
>
><pre caption="Checking for correct binutils">
># cd /etc/env.d/binutils/
># ls -la
>total 8
>-rw-r--r-- 1 root root 15 Sep 3 13:48 config-i686-pc-linux-gnu
>-rw-r--r-- 1 root root 126 Sep 3 13:48 i686-pc-linux-gnu-2.16.1
>
># cat config-i686-pc-linux-gnu
>CURRENT=2.16.1
># cat i686-pc-linux-gnu-2.16.1
>TARGET="i686-pc-linux-gnu"
>VER="2.16.1"
>LIBPATH="/usr/lib/binutils/i686-pc-linux-gnu/2.16.1"
>FAKE_TARGETS="i686-pc-linux-gnu"
></pre>
>
>
>That one looks good, those two files actually should be there. Time to move on
>to the gcc directory.
>
>
><pre caption="Checking for correct gcc">
># cd /etc/env.d/gcc
># ls -la
>total 12
>-rw-r--r-- 1 root root 32 Sep 3 16:43 config
>-rw-r--r-- 1 root root 32 Aug 3 14:25 config-i386-pc-linux-gnu
>-rw-r--r-- 1 root root 292 Sep 3 16:43 i686-pc-linux-gnu-4.1.1
>
># cat config
>CURRENT=i686-pc-linux-gnu-4.1.1
>
># cat config-i386-pc-linux-gnu
>CURRENT=i386-pc-linux-gnu-4.1.1
>
># cat i686-pc-linux-gnu-4.1.1
>PATH="/usr/i686-pc-linux-gnu/gcc-bin/4.1.1"
>ROOTPATH="/usr/i686-pc-linux-gnu/gcc-bin/4.1.1"
>LDPATH="/usr/lib/gcc/i686-pc-linux-gnu/4.1.1"
>GCCBITS="32"
>MANPATH="/usr/share/gcc-data/i686-pc-linux-gnu/4.1.1/man"
>INFOPATH="/usr/share/gcc-data/i686-pc-linux-gnu/4.1.1/info"
>STDCXX_INCDIR="g++-v4"
></pre>
>
>
><path>config</path> and <path>i686-pc-linux-gnu-4.1.1</path> are fine,
>but <path>config-i386-pc-linux-gnu</path> is another leftover that needs
>removal.
>
>
><note>
>Again, the name of the file containing references to an outdated gcc version
>may have a different name, e.g. config-i686-pc-linux-gnu even though you are
>changing to i686. It is important you identify the file on its content, not
>only the name.
></note>
>
><pre caption="Removing the incorrect gcc config file">
># rm config-i386-pc-linux-gnu
></pre>
>
>
>now run:
>
>
><pre caption="Updating the environment">
># env-update &amp;&amp; source /etc/profile
></pre>
>
>
>Then verify everything is fixed:
>
>
><pre caption="Verifying refernces to the old CHOST are removed">
># grep -r 386 /etc/env.d/
></pre>
>
>
>If you still find something, you must have missed some file, try to track
>it down before going on.
>
>
></body>
></section>
><section>
><title>Finishing The Change</title>
><body>
>
>
>Now it is necessary to re-emerge <c>libtool</c> and run <c>fix_libtool_files.sh</c>.
>Make sure to use the correct gcc version (your current one, 4.1.1 here, and
>the old architecture (i386 here)).
>
>
><pre caption="Ensuring library sanity">
># emerge -av1 libtool
># fix_libtool_files.sh 4.1.1 --oldarch i386-pc-linux-gnu
></pre>
>
>
>You may want to run:
>
>
><pre caption="Rebuilding world">
># emerge -e world
></pre>
>
>
>Now, in theory it should not be necessary to do so, but it can not be
>100% guaranteed that this is actually the case. ;-) If you do not recompile the
>world target, i've been told at least some packages need recompiling, so you should do:
>
>
><pre caption="Remerging python and groff">
># emerge -av1 python groff
></pre>
>
>All packages using perl install to the CHOST directory and hence need 
>remerging. In case you haven't installed qfile, you will need to install
>app-portage/portage-utils first
>
><pre caption="Remerging perl packages">
># emerge -av portage-utils
># emerge -av1 `qfile /usr/lib/perl* -Cq | sort -u`
></pre>
>
>If you have installed courier / courier-imap - series, it is highly
>recommended to recompile all these packages, including courierauth. 
>Otherwise your won't be able to use any courier services because login will
>fail.
>
>
><pre caption="Remerging courier related packages if necessary">
># emerge -av1 courier courier-authlib courier-imap
></pre>
>
>
>If you encounter other packages that need recompiling, please let me know at the
>the email below.
>
>
>
>That should be all, feedback (both if it worked, failed or other problems
>were encountered) is welcome, please send an email to <mail>amne@gentoo.org</mail> or post
>to <uri link="http://forums.gentoo.org/viewtopic-t-494147.html">this forums thread</uri>
>Much in this howto comes from vapier, thanks for your help!
>
>
></body>
></section>
></chapter>
></guide>

Actions: View

Attachments on bug 147502: 96906 | 97342 | 97343 | 97365 | 97820