summaryrefslogtreecommitdiffstats
path: root/results/classifier/108/other/1861341
diff options
context:
space:
mode:
Diffstat (limited to 'results/classifier/108/other/1861341')
-rw-r--r--results/classifier/108/other/186134152
1 files changed, 52 insertions, 0 deletions
diff --git a/results/classifier/108/other/1861341 b/results/classifier/108/other/1861341
new file mode 100644
index 00000000..e2f9a5bb
--- /dev/null
+++ b/results/classifier/108/other/1861341
@@ -0,0 +1,52 @@
+device: 0.708
+graphic: 0.635
+semantic: 0.554
+files: 0.529
+socket: 0.466
+PID: 0.443
+other: 0.391
+performance: 0.389
+network: 0.383
+permissions: 0.359
+boot: 0.356
+vnc: 0.355
+debug: 0.124
+KVM: 0.096
+
+ARM QEMU: Unknown syscall 397
+
+QEMU is reporting
+
+```
+Unknown syscall 397
+```
+
+(statx if I read tables right) when used via flatpak for ARM images on x86_64. This has been reproduced on Fedora and Gentoo.
+
+To reproduce:
+
+- get flatpak KDE 5.12 for arm:
+
+flatpak install --user org.kde.Sdk/arm/5.12 org.kde.Platform/arm/5.12
+
+
+- run qmake inside Sdk:
+
+QEMU_STRACE=1 flatpak run --filesystem=host --command=qmake org.kde.Sdk/arm/5.12 .
+
+
+You will get a host of messages with unknown syscall. In practice, qmake will fail to find .pro files if you have them in that folder and libraries in the system.
+
+As far as I understand, Flatpak images are built on AARCH64 hardware.
+
+My config on Gentoo:
+
+kernel: 4.19.86-gentoo x86_64
+app-emulation/qemu: ~4.2.0-r1 , same with 4.0.0
+
+New syscall definitions for ARM have been added lately by:
+
+73209e1f15c6 ("linux-user: arm: Update syscall numbers to kernel 5.5 level")
+
+It will available in QEMU 5.0
+