blob: 8e11e275f9a8d4f9c2ee43096f36446f00071f00 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
|
<think>
Okay, I'm trying to figure out whether this QEMU bug is user-mode or system-mode related. The problem occurs during a static build using the native AArch64 toolchain on ArchlinuxARM. The error message points to issues during linking, specifically mentioning problems with ld and certain relocation errors.
Looking at the steps provided, the user is configuring QEMU with several options, but notably enabling Linux-user mode and TCG (which I think stands for Tiny Code Generator). They're disabling system-mode components like KVM and other device emulations. This suggests they are focusing on user-mode execution where QEMU runs binaries without full OS emulation.
The error messages mention functions from glibc's database entries, which are typically used in user applications. The linker is complaining about using 'getpwuid' and similar functions in a static build, which usually require shared libraries at runtime. This ties into how the application interacts with system libraries, something more common in user-mode where binaries rely on libc for system calls.
Also, the target being built is qemu-aarch64_be, which I believe is meant to run AArch64 big-endian binaries in user mode. The fact that it's a static build complicates things because static binaries don't link against shared libraries at runtime, but certain functions still require dynamic linking elements.
The error about relocation and GOT entries seems related to how the binary is linked, which could be an issue with position-independent code (PIC) versus non-PIC. The linker suggests recompiling with -fPIC, indicating that maybe some object files aren't built correctly for static linking.
Considering all this, the problem seems tied to user-mode because it's about running binaries without full OS-level device emulation. It involves issues with how QEMU links against system libraries and handles functions typically used in userspace applications.
</think>
The bug report is related to a user-mode issue as indicated by the build configuration focusing on Linux-user mode and the linking problems encountered.
user
|