Just grabbed these ebuilds today to try a 2.6 test kernel on my spare ultra box.

binutils seems to have built fine, but when i try to grab gcc, none of the mirrors have the file its looking for. Get the following error:

!!! Couldn't download gcc-sparc64-3.2.2.tar.bz2. Aborting.

I looked into the binutils ebuild, and saw that it seems to download plain old binutils, so i took out some of the code in the gcc ebuild, and it fails to build.
SRC_URI="ftp://gcc.gnu.org/pub/gcc/releases/${NEWP}/${P}.tar.bz2"

turned it into this, and no go:
SRC_URI="ftp://gcc.gnu.org/pub/gcc/releases/${NEWP}.tar.bz2"

any assistance would be great_________________-Todd <todd@gentoo.org>
-Gentoo/SPARC Developer

I'm just wondering, if you are not running any programs that require large numbers, is there much of an advantage for a standard workstation to have all 64-bit userland? My understanding is that the Gentoo Kernel on SPARC is 64-bit, is that a correct understanding?

Just not sure exactly what the major advantage is. I know Solaris has been 64-bit for sometime, but I don't see the advantage there either. Our use of the Solaris does not seem to take much advantage of 64-bit .

- For every userland program which has to interact with kernel space data, they might work in full 32-bit and full 64-bit but not the mix. (this should be fixed by the developer, if you are running all 64-bit you won't have the problem)

- For every userland program which has to interact with kernel space data, they might work in full 32-bit and full 64-bit but not the mix. (this should be fixed by the developer, if you are running all 64-bit you won't have the problem)

xming

Perhaps I'm confused. When I compile my kernel on Gentoo SPARC, it is using a different compiler? Granted, I've just started my first Gentoo-SPARC installation, so I have no direct experience with it yet.