Hi all,
(Apologies for this cryptic subject. Lemme explain the issue I'm facing.)
I'm using proot to build a number of packages for my target
(target=arm ; host=x86_64).
Everything works fine until CMake-based packages is built.
When trying to build cmake, during it bootstrap step, cmake uses its
own binary (a minimal one) to configure itself (the final program).
During cmake checks, qemu become zombi at some point, this does not
seems correctly catched by cmake, so it endlessly hangs... :-(
Here is some the end of the cmake log (in an emerge build), and the
process tree when everything is blocked:
http://code.bulix.org/2ie7jo-86676
Note:
- to get my proot shell back, I have to kill the build;
- it hangs at different point (not always the same check);
- if I load my system, cmake in proot may run correctly;
- I unsuccessfully try to attach a gdb on qemu or cmake to know where it hangs.
- an easy setup to reproduce the issue is: just trying to build cmake
using a stage3 (from gentoo or something else), this is not related to
emerge.
I don't really know where to look: is this a cmake issue, or a qemu
one or a proot one?
Any pointer how to investigate this is welcome.
Regards,
--
Samuel