Gentoo Archives: gentoo-user

From: Mark Shields <laebshade@×××××.com>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] Changing CHOST
Date: Mon, 24 Sep 2007 02:32:46
Message-Id: 642958cc0709231916v4588201cuc264f745ff202aee@mail.gmail.com
In Reply to: [gentoo-user] Changing CHOST by David Relson
1 On 9/22/07, David Relson <relson@×××××××××××××.com> wrote:
2 >
3 > Now that my old AthlonXP mobo has been replaced by an AMD 64 X2 mobo,
4 > it's time for upgrading CHOST :->
5 >
6 > According to http://www.gentoo.org/doc/en/change-chost.xml after a
7 > couple of changes to /etc/make.conf, i.e.
8 >
9 > from:
10 > USE="x86 ..."
11 > CHOST="i686-pc-linux-gnu"
12 > CFLAGS="-O2 -march=athlon-xp -pipe"
13 >
14 > to:
15 > USE="amd64 ..."
16 > CHOST="amd64-pc-linux-gnu"
17 > CFLAGS="-O2 -march=x86-64 -pipe"
18 >
19 > The next step is:
20 >
21 > emerge -av1 binutils gcc glibc
22 >
23 > The emerge of binutils works fine. However the emerge of gcc fails
24 > with:
25 >
26 > In file included from .../gcc/unwind-dw2.c:257:
27 > gcc/config/i386/linux-unwind.h: In function
28 > 'x86_64_fallback_frame_state':
29 > gcc/config/i386/linux-unwind.h:63:
30 > error: 'struct sigcontext' has no member named 'rsp'
31 >
32 > A quick search of BGO didn't show anything relevant.
33 >
34 > Any suggestions???
35 >
36 > Thanks.
37 >
38 > David
39 > --
40 > gentoo-user@g.o mailing list
41 >
42 >
43 Besides what everyone else has already suggested, I would suggest backing up
44 everything beforehand, or you can continue using your 32-bit environment
45 with your shiny new 64-bit processor, but you will not be able to use any
46 64-bit binaries.
47
48 --
49 - Mark Shields

Replies

Subject Author
Re: [gentoo-user] Changing CHOST David Relson <relson@×××××××××××××.com>