On 07/01/2012 01:41 PM, Thomas Sachau wrote: > I guess, you are mixing cross-compile support in multilib profiles and > cross-compile support with cross-toolchains, multilib-portage is for the > first one, while crossdev is for the second one. > > My suggestion does not support e.g. compiling for ppc with an amd64 > profile, on amd64 it only can support x86 and x32. Since all of these > binaries can run with an amd64 kernel and you build for at least one > target, you always have a binary around, no need for an extra HOST > dependency.
You can run an arm binary on amd64 (through binfmt+qemu-user static) > I dont know, what exactly you mean with "play properly with ld" and > "cross-vs-host paths", so cannot respond to those. multilib works because the runtime linker picked is the right one for each ABI, thanks to qemu makes no difference if that ABI is native or not. cross vs host paths is an annoying problem due the slightly different behaviour between native and cross compiler toolchains, it tends to ignore environment variables and other small differences making dropping an native cross compiler in a qemu chroot, QUITE a creative activity. lu -- Luca Barbato Gentoo/linux http://dev.gentoo.org/~lu_zero
