Re: [gentoo-alt] How to make prefix using new glibc ?

[Galaxy]

qdepends gcc-4.4
sys-devel/gcc-4.4.3-r2: >=sys-libs/zlib-1.1.4 >=sys-devel/gcc-config-1.4 virtual/libiconv >=dev-libs/gmp-4.2.1 >=dev-libs/mpfr-2.3.2 >=sys-libs/ncurses-5.2-r2 sys-devel/gettext >=sys-apps/texinfo-4.8 >=sys-devel/bison-1.875 >=sys-libs/glibc-2.8 >=sys-devel/binutils-2.15.94 sys-devel/gnuconfig >=sys-apps/sed-4

The '>=sys-libs/glibc-2.8' indicate that I can never run gcc-4.4 under glibc-2.4.
That is why I need to prefix another glibc.

About kernel, since it cannot be done without root private, I will not try that.

I think the benefit of a prefixed environment is to make us run things that the root are too lazy to enable.
And this kind of root is what I am facing.

> On 08/17/10 01:14, Galaxy wrote:

>> I googled and find http://www.nslu2-linux.org/wiki/HowTo/SetUpAToolChainOnAMac ,
>>  which says that it is possible to compile a GNU tool chain over Mac OS X, a BSD release.
>> And since it works on BSD with some tweaks, it should also works on Linux.

> I'm exposing my ignorance here, but I really don't think you need all
> that.  The page linked above seems to deal with cross-compiling for ARM,
> which I think is a different problem from what you're having.

> As I think of it, libc isn't really part of your toolchain, but rather
> your interface to the system (kernel) on which your prefix is running.
> You may be able to compile your own libc--whether it's GNU's or somebody
> else's--but then you've just moved the prefix-system interface from libc
> to the kernel, and you've got to (manually) ensure that your libc plays
> nice with all the kernels you intend to use your prefix on.  You may
> similarly be able to compile a kernel with your prefix software, but
> then you've really lost the benefit of the prefixed environment.

> // Cheers; Johan