blob: 38412884fa376515caa6b9ee6547ae4f496a7007 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
|
device: 0.708
graphic: 0.635
instruction: 0.605
semantic: 0.554
socket: 0.466
other: 0.391
network: 0.383
boot: 0.356
vnc: 0.355
mistranslation: 0.311
assembly: 0.113
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
|