blob: 7f1929ebb380463ff8f17349c0e5b30a6f8e27ee (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
|
<think>
Okay, so I'm trying to figure out whether this bug report about QEMU is related to user-mode or system-mode issues. Let me break it down.
The problem occurs during the build of Yocto/bitbake cross tools, specifically when configuring SDL for QEMU-2.2.0. The issue arises in the "SDL probe" step where a test compile links but fails because it can't find libncursesw. The user had to install libncursesw5-dev to fix it and adjusted the configuration script by adding the library path.
Hmm, user-mode vs system-mode... User-mode issues usually involve applications running with standard user privileges without needing special permissions or device access. System-mode involves lower-level stuff like kernel interactions, hardware drivers, or services that require higher privileges.
In this case, the issue is during a build process. Building software typically runs in user-mode unless it's something like compiling a kernel module. The error here is about linking against a library, which doesn't seem to involve device access or system-level operations. It's more about dependencies and configuration scripts, which are part of building applications.
So, since the problem is about a build script failing due to missing libraries and linker issues, it's likely a user-mode issue. The fix was adjusting the linker path in the script without needing any system-level changes or privileges.
</think>
user
|