RE: Gcc+binutils+libc cross-compiling: path to libc.so.6 malformed in "ld".

["Kaz Kylheku" <kaz@zeugmasystems.com>]

> Kai Ruottu wrote: 
>  What I have thought being the aim in producing a "normal" glibc,
> one which should work both as a "native" glibc, and as a "cross"
> glibc, is using the '--prefix=/usr'.

In my case, my native system is x86, and the cross one is MIPS.

Even if the architectures are the same, I don't believe in
mixing target code with the development platform. There is
the potential to screw things up.

If you're cross-compiling, you should run the code on the
target system, or in some isolated environment on the development
system (emulator with support for a different CPU if necessary,
chrooted tree, ...).  With chroot, you can have the library
installed in /lib, exactly as on the target.

There is the problem of sharing the same kernel as the host
system too. On my development system, I might be running some
old kernel, but want a newer one underneath the target glibc.

> 
>      make install_root=$sysroot

I patched glibc's configure.in and config.make to support
--with-sysroot, which sets up that variable at configuration time.

It's surprising that such an important variable is left out from
the configuration.