Hello. I'm in the process of upgrading my organization's development environment from 2023.2 to 2024.1 and encountered this issue. We can easily work around it with a patch in our layers, but I thought I'd bring it to your attention.
It looks like in 2024.1 qemu-system-aarch64-multiarch received some changes, one of which was to exit(1) in response to --help: https://github.com/Xilinx/meta-xilinx/blob/master/meta-xilinx-core/recipes-devtools/qemu/files/qemu-system-aarch64-multiarch#L42 In our environment this is causing a failure when we use "runqemu" without the "nographic" option. For us, it makes it to this line: https://github.com/Xilinx/poky/blob/rel-v2024.1/scripts/runqemu#L1391 subprocess.check_output() detects that the command exited with non-zero status and throws an exception. If I simply patch that qemu-system-aarch64-multiarch script to exit(0) then our regular workflow works again. Thanks, Corey
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#5437): https://lists.yoctoproject.org/g/meta-xilinx/message/5437 Mute This Topic: https://lists.yoctoproject.org/mt/107005905/21656 Group Owner: [email protected] Unsubscribe: https://lists.yoctoproject.org/g/meta-xilinx/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
