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