Jan-Simon, Thank you for your attention. The story of qemu is:
1. In the building, both OBS and gbs, the scripts will use qemu-arm-static to run arm binary inside build env chroot 2. In the ideal settings, we'd like to run 64bit qemu-arm-statis in 64bit host system, and the same for 32bit. AND we'd better use the qemu from Tizen repo. 3. In the 32bit host system, 32bit qemu will encounter memory faults when compiling eglibc of tizen-2.2, so we must use others to bypass it. 32bit system. 4. But now, for tizen-3.0, eglibc will not be used. So the issue is not critical. But tools need to continue the support for tizen-2.1/2.2. Anyway, it's a very corner issue. thanks - jf.ding On Mon, Sep 23, 2013 at 03:47:27PM +0200, Jan-Simon Möller wrote: > On Monday 23 September 2013 13:52:56 Jian-feng Ding wrote: > > > if the problem is qemu on 32bit x86 emulating arm... mayhaps we should > > > talk > > > about that issue itself? i remember there being memory mapping > > > conflicts/issues in doing misc binary emul, but i don't remember the > > > details anymore. > > Besides qemu's issue, and there are some build issues for baselibs, as I > > remember. And it's already half a year it cannot be resolved. It's tricky > > but we have workaround solution already, but it will also affect the tools > > quality. > > Tell us more about it. We are here to help solving those issues. > > What is the qemu issue? > > What is the baselibs issue ? > > Best, > Jan-Simon Möller _______________________________________________ General mailing list [email protected] https://lists.tizen.org/listinfo/general
