1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
|
<think>
Alright, let's try to figure out which category this bug report falls into. The user is encountering an issue when using QEMU with x86_64 during their build process for an embedded Linux system. They're getting errors about missing GLIBCXX and GLIBC versions.
Looking at the error messages, it seems like QEMU is trying to use host libraries instead of the emulated ones. The log shows that the linker is looking in the host's /usr/lib and /lib directories, which isn't what they want for their cross-compiled system. They mentioned using Buildroot and a hack with QEMU, so I think this relates to how QEMU sets up the environment.
The possible categories include things like mistranslation, assembly lowering, device, graphic, socket, network, KVM, boot, vnc, debug, files, permissions, performance, kernel, peripherals, hypervisor, and others.
Since the issue is about library paths and which libraries are being used during execution, it's likely related to how QEMU handles the system calls or emulation of the target environment. The problem isn't with translating code incorrectly (so not mistranslation) nor is it an assembly lowering issue. It doesn't seem to be a performance or kernel issue either.
The user is using QEMU to run their application, so perhaps this is related to how QEMU's hypervisor function sets up the environment. The fact that it's picking up host libraries instead of emulated ones suggests a configuration or setup problem in the emulation process, which falls under hypervisor category as it pertains to how the virtual machine is set up.
I think 'hypervisor' is the right category because the issue revolves around QEMU's role as a hypervisor and its proper setup of the guest environment, including library paths. It's not about device drivers or graphics but rather about system-level configuration during emulation.
</think>
The bug report describes an issue where QEMU is incorrectly using host libraries instead of emulating the target system's libraries when running applications cross-compiled for x86_64. This pertains to how the hypervisor sets up the environment and ensures that the guest system uses its own libraries rather than those from the host.
**Answer:** hypervisor
|