Re: ppc64 port
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I think bens onto something. Get a 64 bit kernel running first
with any form of 32/64bit user interface then you can debate
the blend of 32/64bit software.
personally, just go 100% 64bit. we dont try to share powerpc
stuff with i386 and also 64bit should take over from 32bit.
64bit has been around long enough, it shouldnt be too big of a
deal to recompile everything (assuming you can get a crosscompiler
or a whole bunch of g5's)
but having said that people are still out there running linux
on pentiums, im sure you could find someone running up to date
software with a 386!
Dean
Benjamin Herrenschmidt wrote:
|>I wouldn't say that. Tedious yes, difficult no.
|
|
| Well... Ask that to all the people I know who tried to do it :) it
| keeps breaking. Every new glibc CVS checkout breaks the build in a
| different way from experience.
|
|
|>Besides, the debian x86_64 folks build bi-arch already. Just grab their
|>build scripts.
|
|
| If they work at all :)
|
| Anyway, whatever the debate is here, the first step is to build a biarch
| compiler with the appropriate libcs. Wether it defaults to 32 or 64 bits
| is probably a detail at this point. Once we have that and thus the ability
| to build ppc64 kernels, we have already a working solution _now_ for
people
| who want to run debian, for example, on js20.
|
| Once that's done, we can eventually focus on a full 64 bits rebuild of all
| package with a gcc configured to default to 64 bits.
|
| Ben.
|
|
|
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFAkGsII1HDX08lY+ARAguDAKCmwO1AKDgQ/PweyFVosvB1Nn6SLQCfZf7R
vqvd3jM8bdZk4eSqLcSg93o=
=OYPM
-----END PGP SIGNATURE-----
Reply to: