| View previous topic :: View next topic |
| Author |
Message |
e-ipi Apprentice


Joined: 23 Aug 2005 Posts: 192
|
Posted: Tue Aug 15, 2006 9:53 pm Post subject: ip30/octane -- which arch? |
|
|
I'm somewhat confused as to which architecture/userland is best for my Octane gentoo install. I gather that I need a 64 bit kernel no matter which way I go, and the handbook suggests that I'll need a 64 bit toolchain to compile my kernels anyway. I don't see any 64 bit stage 3 tarballs, and there are postings from about a year ago warning against n32. Do those warnings still apply?
Bear in mind that nothing on this machine is "mission critical" or "production" or anything like that -- it's 100% hobby. |
|
| Back to top |
|
 |
Redhatter Retired Dev


Joined: 20 Sep 2003 Posts: 548 Location: Brisbane, QLD, Australia
|
Posted: Wed Aug 16, 2006 1:55 am Post subject: |
|
|
You use the 32-bit ones... the 64-bit toolchain is installed by merging the kgcc64 ebuild. _________________ Stuart Longland (a.k.a Redhatter, VK4MSL)
I haven't lost my mind - it's backed up on a tape somewhere...
Gentoo/MIPS Cobalt developer, Mozilla herd member. |
|
| Back to top |
|
 |
Kumba Developer


Joined: 16 Jul 2002 Posts: 364 Location: Byzantine Secundus, Antarctica
|
Posted: Thu Aug 17, 2006 9:17 pm Post subject: Re: ip30/octane -- which arch? |
|
|
| e-ipi wrote: | | I'm somewhat confused as to which architecture/userland is best for my Octane gentoo install. I gather that I need a 64 bit kernel no matter which way I go, and the handbook suggests that I'll need a 64 bit toolchain to compile my kernels anyway. I don't see any 64 bit stage 3 tarballs, and there are postings from about a year ago warning against n32. Do those warnings still apply? |
Yeah, for Octane, you'll be using a mixed environment -- 64bit kernel with 32bit userland. As Redhatter mentioned, the sys-devel/kgcc64 package, which replaces sys-devel/gcc-mips64, builds you a simple kernel compiler (that is, it only builds kernels, nothing else). The system compiler continues to generate 32bit binaries.
As for n32, yes, those warnings are technically still in effect. For now, we prefer the only people toying with n32 to be people skilled enough and willing enough to contribute patches back. This means any such people will find themselves attempting to debug the kernel, toolchain, or even the C library (glibc, uclibc). n32 still has known issues, and although one can get a usable userland out of it, it's not considered practical or safe for normal use by anyone and everyone.
--Kumba _________________ "Though the mills of God grind slowly, yet they grind exceeding small; Though with patience He stands waiting, with exactness grinds He all."
--Friedrich Vón Logau |
|
| Back to top |
|
 |
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|