On Tue, 21 Nov 2023 at 12:12, Jose Quaresma <quaresma.j...@gmail.com> wrote: >> I was using it for running Unit Tests on the host before I deployed >> them to the target device as ptest. This worked well. It is well >> integrated with cmake and therefore also with IDEs. So I thought that >> there are certain use cases where it would be nice to have it opt-in. >> >> meson offers qemu-user as well (because of gobject). So if qemu-user is >> not usable there will be other challenges as well. >> >> There is also a MACHINE_FEATURE which allows to support it for ARCHs >> where it works well but not for ARCHs where qemu-user is known to be >> broken. >> >> I think it would be a nice optional feature. > > > I agree without any doubt on that part. > > But I believe this doesn't work for applications that are using the fork > system call. > So consider this will also break any ptest using fork, giving the wrong > impression the test is failing.
I think this needs to be double checked. I find it odd that qemu usermode would fail on such a basic thing, and it would not show up anywhere in places where it's used in core (not just g-i - all the various postinst utilities for generating indexes etc.). Alex
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#190965): https://lists.openembedded.org/g/openembedded-core/message/190965 Mute This Topic: https://lists.openembedded.org/mt/102708283/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
