Whoever wrote:
>
>
> On Thu, 14 Dec 2006, Sebastian Volke wrote:
>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> | ----- Original Message -----
>> | From: Whoever <nobody@devnull.none>
>> | Sent: 12/12/2006 2:36:58 AM +0100
>> | Subject: Converting to 64-bit
>> |
>> | If the 64-bit conversion is not practical, currently (for historical
>> | reasons), I have been using "CHOST=i586-pc-linux-gnu" (although I also
>> | have "-march=athlon"), how should I convert to a more appropriate
>> CHOST?
>>
>> If you're really serious about changing the CHOST, you may (or may not)
>> find something helpful about it at
>> http://www.gentoo.org/doc/en/change-chost.xml.
>> Converting to amd64 over time looks difficult to me, because running 32
>> and 64-bit programms at the same time is impossible.
>> I myself use a amd64 profile with multilib support, so I can run 32-bit
>> and 64-bit binaries. But: it is necessary, that EVERY library a 32-bit
>> binary needs, is available under /lib32/ or /usr/lib32/. 32-bit binaries
>> only work with 32-bit libraries, as 64-bit binaries only load 64-bit
>> libraries.
>> So it looks rather impossible to me to convert to 64-bit "over time".
>
> I started to try to build a new 64-bit system in a chroot environment,
> but have run into a problem:
> chroot: cannot run command `/bin/bash': Exec format error

The 32bit kernel do not have any 64bit support, so you can't run 64bit
programs without using an emulator, not sure if qemu can help you here.


> I assume that this is because the kernel doesn't recognise 64-bit
> binaries. I have previously selected Opteron/Athlon64 for my processor
> sub-architecture and rebuilt the kernel and rebooted. Yet uname still
> shows it as i686:

You can build a 64bit kernel with support for 32bit, this may work.
On Sparcs you use 64bit kernel with a 32bit userspace, as you don't gain
anything really using 64bit for quite standard systems (on heavy calculating
systems you would).


--

//Aho