blob: 26d008e2a7f3241e778f76ff5fc15b62c20e0ed3 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
|
<think>
Okay, I'm trying to help classify this bug report for QEMU. The user is having trouble static compiling QEMU 7.0.0 on an aarch64 system. They mentioned they want to use it with podman for simulating amd64 containers within a chroot environment.
Looking at the error messages, there are several warnings about using functions like 'getpwuid' and others in a statically linked application. These warnings suggest that certain glibc functions aren't properly handled when static linking. The linker is also complaining about relocations and GOT entries, which relates to position-independent code (PIC) issues.
The user is compiling QEMU for aarch64 in Linux-user mode, as indicated by the target_aarch64_be-linux-user and the presence of elfload.c.o and other linux-user specific files. This tells me they're aiming to run x86_64 binaries on an aarch64 host, which is user-mode emulation.
The errors are happening during the linking phase when trying to create the qemu-aarch64_be executable. The fact that it's about static compilation and runtime dependencies suggests it's related to how the userland processes are being emulated, not the system-level hypervisor or machine emulation.
So putting this together, since they're targeting user-mode (linux-user) and dealing with static linking issues specific to running other architectures' binaries, this bug is classified under 'user'.
</think>
The error occurs while compiling QEMU for aarch64 in user mode. The issue arises during static linking, specifically due to problems with certain glibc functions and PIC relocations, which are common in user-mode emulations.
**Answer:**
user
|