[gentoo-user] Changing CHOST

[gentoo-user] Changing CHOST

[David Relson]

Now that my old AthlonXP mobo has been replaced by an AMD 64 X2 mobo,
it's time for upgrading CHOST :->

According to http://www.gentoo.org/doc/en/change-chost.xml after a
couple of changes to /etc/make.conf, i.e.

  from:
       USE="x86 ..."
       CHOST="i686-pc-linux-gnu"
       CFLAGS="-O2 -march=athlon-xp -pipe"

  to:
      USE="amd64 ..."
      CHOST="amd64-pc-linux-gnu"
      CFLAGS="-O2 -march=x86-64 -pipe"

The next step is:

    emerge -av1 binutils gcc glibc

The emerge of binutils works fine.  However the emerge of gcc fails
with:

  In file included from .../gcc/unwind-dw2.c:257:
  gcc/config/i386/linux-unwind.h: In function
     'x86_64_fallback_frame_state': 
  gcc/config/i386/linux-unwind.h:63:
    error: 'struct sigcontext' has no member named 'rsp'

A quick search of BGO didn't show anything relevant.

Any suggestions???

Thanks.

David
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Changing CHOST

[Bo Ørsted Andresen]

[-- Attachment #1: Type: text/plain, Size: 812 bytes --]

On Sunday 23 September 2007 02:13:46 David Relson wrote:
> Now that my old AthlonXP mobo has been replaced by an AMD 64 X2 mobo,
> it's time for upgrading CHOST :->
>
> According to http://www.gentoo.org/doc/en/change-chost.xml after a
> couple of changes to /etc/make.conf, i.e.
>
>   from:
>        USE="x86 ..."
>        CHOST="i686-pc-linux-gnu"
>        CFLAGS="-O2 -march=athlon-xp -pipe"
>
>   to:
>       USE="amd64 ..."
>       CHOST="amd64-pc-linux-gnu"
>       CFLAGS="-O2 -march=x86-64 -pipe"
[SNIP]

Changing CHOST is valid when you have e.g. an i386 CHOST and want to change it 
to i686. It is not an option for going from 32 bit to 64 bit. You need to 
reinstall. Also.. don't set x86 or amd64 in USE manually! And finally x86-64 
is not a valid march...

-- 
Bo Andresen

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] Changing CHOST

[Albert Hopkins]

On Sun, 2007-09-23 at 03:43 +0200, Bo Ørsted Andresen wrote:
> Changing CHOST is valid when you have e.g. an i386 CHOST and want to
> change it 
> to i686. It is not an option for going from 32 bit to 64 bit. You need
> to 
> reinstall. 

Below is what I did a few years ago.  YMMV.  There may be a better guide
on the Wiki or somewhere.

--
Albert W. Hopkins

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Changing CHOST

[Albert Hopkins]

Oops, forgot to paste the link:

http://starship.python.net/crew/marduk/blog/entry/1112117933.9,14473

--
Albert W. Hopkins

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Changing CHOST

[Volker Armin Hemmann]

On Sonntag, 23. September 2007, David Relson wrote:
> Now that my old AthlonXP mobo has been replaced by an AMD 64 X2 mobo,
> it's time for upgrading CHOST :->
>
> According to http://www.gentoo.org/doc/en/change-chost.xml after a
> couple of changes to /etc/make.conf, i.e.
>
>   from:
>        USE="x86 ..."
>        CHOST="i686-pc-linux-gnu"
>        CFLAGS="-O2 -march=athlon-xp -pipe"
>
>   to:
>       USE="amd64 ..."
>       CHOST="amd64-pc-linux-gnu"
>       CFLAGS="-O2 -march=x86-64 -pipe"
>
> The next step is:
>
>     emerge -av1 binutils gcc glibc
>
> The emerge of binutils works fine.  However the emerge of gcc fails
> with:
>
>   In file included from .../gcc/unwind-dw2.c:257:
>   gcc/config/i386/linux-unwind.h: In function
>      'x86_64_fallback_frame_state':
>   gcc/config/i386/linux-unwind.h:63:
>     error: 'struct sigcontext' has no member named 'rsp'
>
> A quick search of BGO didn't show anything relevant.
>
> Any suggestions???
>
> Thanks.
>
> David

boot from cd
mkfs.reiserfs
start stage3 installation.

It is the only safe way. It is faster and much less problematic.
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Changing CHOST

[Doug Whitesell]

On Sep 23, 2007, at 5:47 AM, Volker Armin Hemmann wrote:

> On Sonntag, 23. September 2007, David Relson wrote:
>> Now that my old AthlonXP mobo has been replaced by an AMD 64 X2 mobo,
>> it's time for upgrading CHOST :->
>>
>> According to http://www.gentoo.org/doc/en/change-chost.xml after a
>> couple of changes to /etc/make.conf, i.e.
>>
>>   from:
>>        USE="x86 ..."
>>        CHOST="i686-pc-linux-gnu"
>>        CFLAGS="-O2 -march=athlon-xp -pipe"
>>
>>   to:
>>       USE="amd64 ..."
>>       CHOST="amd64-pc-linux-gnu"
>>       CFLAGS="-O2 -march=x86-64 -pipe"
>>
>> The next step is:
>>
>>     emerge -av1 binutils gcc glibc
>>
>> The emerge of binutils works fine.  However the emerge of gcc fails
>> with:
>>
>>   In file included from .../gcc/unwind-dw2.c:257:
>>   gcc/config/i386/linux-unwind.h: In function
>>      'x86_64_fallback_frame_state':
>>   gcc/config/i386/linux-unwind.h:63:
>>     error: 'struct sigcontext' has no member named 'rsp'
>>
>> A quick search of BGO didn't show anything relevant.
>>
>> Any suggestions???
>>
>> Thanks.
>>
>> David
>
> boot from cd
> mkfs.reiserfs
> start stage3 installation.
>
> It is the only safe way. It is faster and much less problematic.
> --  
> gentoo-user@gentoo.org mailing list
>
This is true and is the recommended way; what Albert posted is almost  
effectively a full reinstall.

I would advocate — and have used — the start-from-scratch process.  
Unpredictable result from anything else, and such ... (For some  
reason it's difficult to go from 486 to 686, although by following  
the posted guidelines at gentoo.org I have never had such trouble...)--
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Changing CHOST

[Doug Whitesell]

On Sep 22, 2007, at 5:13 PM, David Relson wrote:

> Now that my old AthlonXP mobo has been replaced by an AMD 64 X2 mobo,
> it's time for upgrading CHOST :->
>
> According to http://www.gentoo.org/doc/en/change-chost.xml after a
> couple of changes to /etc/make.conf, i.e.
>
>   from:
>        USE="x86 ..."
>        CHOST="i686-pc-linux-gnu"
>        CFLAGS="-O2 -march=athlon-xp -pipe"
>
>   to:
>       USE="amd64 ..."
>       CHOST="amd64-pc-linux-gnu"
>       CFLAGS="-O2 -march=x86-64 -pipe"
>
> The next step is:
>
>     emerge -av1 binutils gcc glibc
>
> The emerge of binutils works fine.  However the emerge of gcc fails
> with:
>
>   In file included from .../gcc/unwind-dw2.c:257:
>   gcc/config/i386/linux-unwind.h: In function
>      'x86_64_fallback_frame_state':
>   gcc/config/i386/linux-unwind.h:63:
>     error: 'struct sigcontext' has no member named 'rsp'
>
> A quick search of BGO didn't show anything relevant.
>
> Any suggestions???
>
> Thanks.
>
You're getting that _specific_ error because there is no register  
'RSP' (the 64-bit stack pointer in the AMD64 world) in the 32-bit x86  
world. (You have a 32-bit stack pointer 'esp' instead.)
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Changing CHOST

[Marc Redmann]

> boot from cd

Don't want to start a flame war here, but why should he use reiserfs ??? I 
think he can use whatever filesystem he wishes to ...

> mkfs.reiserfs
> start stage3 installation.

brgds, Marc
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Changing CHOST

[Volker Armin Hemmann]

On Sonntag, 23. September 2007, Marc Redmann wrote:
> > boot from cd
>
> Don't want to start a flame war here, but why should he use reiserfs ??? 

it was an example. And I am free to choose any fs I want for that. Exept jfs. 
Besides reiserfs is a good fs, so no harm done.
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Changing CHOST

[Mark Shields]

[-- Attachment #1: Type: text/plain, Size: 1298 bytes --]

On 9/22/07, David Relson <relson@osagesoftware.com> wrote:
>
> Now that my old AthlonXP mobo has been replaced by an AMD 64 X2 mobo,
> it's time for upgrading CHOST :->
>
> According to http://www.gentoo.org/doc/en/change-chost.xml after a
> couple of changes to /etc/make.conf, i.e.
>
>   from:
>        USE="x86 ..."
>        CHOST="i686-pc-linux-gnu"
>        CFLAGS="-O2 -march=athlon-xp -pipe"
>
>   to:
>       USE="amd64 ..."
>       CHOST="amd64-pc-linux-gnu"
>       CFLAGS="-O2 -march=x86-64 -pipe"
>
> The next step is:
>
>     emerge -av1 binutils gcc glibc
>
> The emerge of binutils works fine.  However the emerge of gcc fails
> with:
>
>   In file included from .../gcc/unwind-dw2.c:257:
>   gcc/config/i386/linux-unwind.h: In function
>      'x86_64_fallback_frame_state':
>   gcc/config/i386/linux-unwind.h:63:
>     error: 'struct sigcontext' has no member named 'rsp'
>
> A quick search of BGO didn't show anything relevant.
>
> Any suggestions???
>
> Thanks.
>
> David
> --
> gentoo-user@gentoo.org mailing list
>
>
Besides what everyone else has already suggested, I would suggest backing up
everything beforehand, or you can continue using your 32-bit environment
with your shiny new 64-bit processor, but you will not be able to use any
64-bit binaries.

-- 
- Mark Shields

[-- Attachment #2: Type: text/html, Size: 2149 bytes --]

Re: [gentoo-user] Changing CHOST

[David Relson]

On Sun, 23 Sep 2007 22:16:03 -0400
Mark Shields wrote:

...[snip]...

> Besides what everyone else has already suggested, I would suggest
> backing up everything beforehand, or you can continue using your
> 32-bit environment with your shiny new 64-bit processor, but you will
> not be able to use any 64-bit binaries.
> 
> -- 
> - Mark Shields

Hi Mark,

Backups happen regularly, so that's not an issue.

I recall installing Gentoo as being a P.I.T.A, hence take no pleasure
in the idea of re-installing.  I was hoping for something relatively
simple, like
   changing CHOST and emerging world
   unpacking amd64 stage3 tarball on top of root
   or something else

Hopefully a year of running Gentoo and emerging regularly and tweaking
config files will make the install less painful.

Regards,

David

P.S.  I did experiment with unpacking the stage3 tarball into a chroot
environment and found that 64-bit ELF executables aren't recognized.
Sigh :-<
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] OT - Changing CHOST

[Rumen Yotov]

On Sun, 23 Sep 2007 23:53:11 +0200
Volker Armin Hemmann <volker.armin.hemmann@tu-clausthal.de> wrote:

> On Sonntag, 23. September 2007, Marc Redmann wrote:
> > > boot from cd
> >
> > Don't want to start a flame war here, but why should he use
> > reiserfs ??? 
> 
> it was an example. And I am free to choose any fs I want for that.
> Exept jfs. Besides reiserfs is a good fs, so no harm done.
Hi,

Using reiser4 on / for 2 weeks and can tell it's very fast&stable.
The speedup is impressive (measured by my time-sense :-)
Before that used reiserfs (3.6) for /.
Rumen
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Changing CHOST

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 924 bytes --]

On Sun, 23 Sep 2007 22:38:36 -0400, David Relson wrote:

> I recall installing Gentoo as being a P.I.T.A, hence take no pleasure
> in the idea of re-installing.  I was hoping for something relatively
> simple, like
>    changing CHOST and emerging world
>    unpacking amd64 stage3 tarball on top of root
>    or something else

Unpacking a stage 3 tarball on top of a working system is a good way of
converting it to a non-working system. It will also overwrite many of
your settings in /etc.

If you are going to use a stage 3 tarball as a basis, a clean stage 3
install is by far the safest option, and usually turns out to be the
quickest too. Backup /etc  and your world file first, use your old
make.conf as a starting point and recreate your old environment on the
new hardware with

emerge -1av $(cat oldworld)


-- 
Neil Bothwick

Electric chairs are period furniture: they end a sentence

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] Changing CHOST

[Florian Philipp]

Neil Bothwick schrieb:
> On Sun, 23 Sep 2007 22:38:36 -0400, David Relson wrote:
> 
>> I recall installing Gentoo as being a P.I.T.A, hence take no pleasure
>> in the idea of re-installing.  I was hoping for something relatively
>> simple, like
>>    changing CHOST and emerging world
>>    unpacking amd64 stage3 tarball on top of root
>>    or something else
> 
> Unpacking a stage 3 tarball on top of a working system is a good way of
> converting it to a non-working system. It will also overwrite many of
> your settings in /etc.
> 
> If you are going to use a stage 3 tarball as a basis, a clean stage 3
> install is by far the safest option, and usually turns out to be the
> quickest too. Backup /etc  and your world file first, use your old
> make.conf as a starting point and recreate your old environment on the
> new hardware with
> 
> emerge -1av $(cat oldworld)
> 
> 
Just a thought: Is it possible to compile a 64bit kernel and use him on
the current system? That way you could set up your new native 64bit
system in a chroot before overwriting the old one and thus minimize
downtime to less than 15 minutes.
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Changing CHOST

[David Relson]

On Mon, 24 Sep 2007 18:17:53 +0200
Florian Philipp wrote:

> Neil Bothwick schrieb:
...[snip]...
> > Unpacking a stage 3 tarball on top of a working system is a good
> > way of converting it to a non-working system. It will also
> > overwrite many of your settings in /etc.
> > 
> > If you are going to use a stage 3 tarball as a basis, a clean stage
> > 3 install is by far the safest option, and usually turns out to be
> > the quickest too. Backup /etc  and your world file first, use your
> > old make.conf as a starting point and recreate your old environment
> > on the new hardware with
> > 
> > emerge -1av $(cat oldworld)
> > 
> > 
> Just a thought: Is it possible to compile a 64bit kernel and use him
> on the current system? That way you could set up your new native 64bit
> system in a chroot before overwriting the old one and thus minimize
> downtime to less than 15 minutes.

Florian,

That would be ideal!  It's exactly what I'd do -- if it's
doable.

Hopefully the experts will point to a HOWTO :->

David
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Changing CHOST

[Doug Whitesell]

On Sep 24, 2007, at 5:03 PM, David Relson wrote:
>> Just a thought: Is it possible to compile a 64bit kernel and use him
>> on the current system? That way you could set up your new native  
>> 64bit
>> system in a chroot before overwriting the old one and thus minimize
>> downtime to less than 15 minutes.
>
> Florian,
>
> That would be ideal!  It's exactly what I'd do -- if it's
> doable.
>
> Hopefully the experts will point to a HOWTO :->
>
This sounds like a way to infinite pain. (This is at first glance and  
off the top of my head without looking into it, of course...) While  
it may be possible to cross-compile a 64-bit kernel on a 32-bit  
system, IIRC unless you have the right runtime libraries compiled for  
64-bit you may have massive trouble getting the system to even come up.

But I'm not an expert on new and cool ways to try things, so your  
mileage may vary.
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Changing CHOST

[Daniel Barkalow]

On Mon, 24 Sep 2007, Florian Philipp wrote:

> Just a thought: Is it possible to compile a 64bit kernel and use him on
> the current system? That way you could set up your new native 64bit
> system in a chroot before overwriting the old one and thus minimize
> downtime to less than 15 minutes.

Building a 64bit kernel with 32bit userspace should be pretty 
straightforward with crossdev (not meaningfully different from building an 
ARM kernel on an x86 host). Building a 64bit userspace while running a 
32bit userspace is a bit trickier. There's some support for building a new 
system with ROOT=/target, but not everything would build like that the 
last time I tried (building for ARM on x86).

	-Daniel
*This .sig left intentionally blank*
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Changing CHOST

[Florian Philipp]

Daniel Barkalow schrieb:
> On Mon, 24 Sep 2007, Florian Philipp wrote:
> 
>> Just a thought: Is it possible to compile a 64bit kernel and use him on
>> the current system? That way you could set up your new native 64bit
>> system in a chroot before overwriting the old one and thus minimize
>> downtime to less than 15 minutes.
> 
> Building a 64bit kernel with 32bit userspace should be pretty 
> straightforward with crossdev (not meaningfully different from building an 
> ARM kernel on an x86 host). Building a 64bit userspace while running a 
> 32bit userspace is a bit trickier. There's some support for building a new 
> system with ROOT=/target, but not everything would build like that the 
> last time I tried (building for ARM on x86).
> 
> 	-Daniel
> *This .sig left intentionally blank*

You don't need to run a 32bit userland (at least not in the way you seem
to think). All you need to do is making your 64bit kernel work with your
current 32bit userland while doing the normal gentoo installation steps
(e.g. extracting stage3 to some folder, chroot into it, updating,
emerging packages needed for your new system, ...).

If it works that way (it sounds far too easy) you could copy config
files and all that stuff from your old system to your new without
shutting down the old one until the new is ready to overwrite the old one.
-- 
gentoo-user@gentoo.org mailing list