blob: e8c1c06b2be3e359cf483df5ce7a660768f85be9 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
|
<think>
Okay, I'm trying to figure out whether this QEMU build issue is a user-mode or system-mode problem. Let's break it down.
The error message says that when building QEMU on CentOS 5.10 with --disable-pie, the linker fails because "-f may not be used without -shared". The problematic commit adds a link flag for stack protection.
Looking at the bisect result, the first bad commit is about linking with -fstack-protector. This affects how binaries are built, possibly requiring shared libraries or specific linker flags.
Since QEMU runs in user mode when emulating guest operating systems and uses various device emulation which is system-level, this build issue touches on both areas. However, the error is during compilation of a client (vscclient), which might be part of the user-mode setup but could also involve system libraries or device handling.
The fact that it's related to linking suggests it's about how components are connected, which can affect the overall QEMU functionality, potentially impacting both user and system modes. But since the bisect points to a commit involving stack protection in build scripts, I think it's more on the lower-level system side because it involves linker flags and library dependencies, which are part of the system setup.
So, after considering all this, I believe this is a system-mode related issue.
</think>
system
|