| 1 |
On 23/03/12 03:36, Jing Huang wrote: |
| 2 |
> 1). Why integrate qemu-user container with crossdev? Crossdev is a cross compiler. |
| 3 |
> The qemu-user container not only compiles the heterogeneous programs but |
| 4 |
> also tests them. I thought if the qemu-user container was good enough, |
| 5 |
> it could replace the crossdev. |
| 6 |
|
| 7 |
qemu is slow, crossdev-generated toolchain is fast. |
| 8 |
|
| 9 |
> 2). "An additional task is to support layered systems so native userspace |
| 10 |
> can be used to further speed up the process (hybrid chroot)." |
| 11 |
> I don't very understand the task. Could someone help me and explain the |
| 12 |
> “hybrid chroot”? |
| 13 |
|
| 14 |
You can mix and match binaries as long you do the right thing with |
| 15 |
ld.so.conf. So you can have the crossdev-generated gcc for the emulated |
| 16 |
targed run inside the chroot and thus fool the broken build systems not |
| 17 |
supporting sanely cross compilation (as in anything but autotools to use |
| 18 |
a broad generalization, people in love with scons, waf and cmake can try |
| 19 |
to fix that, I gave up and I ended up running qemu-user-static |
| 20 |
specifically for those programs, perl and python) |
| 21 |
|
| 22 |
lu |
| 23 |
|
| 24 |
-- |
| 25 |
|
| 26 |
Luca Barbato |
| 27 |
Gentoo/linux |
| 28 |
http://dev.gentoo.org/~lu_zero |
Archives