blob: 3fe63c14665aa610ff54398f1c1f255d36256a6a (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
|
<think>
Okay, so I need to figure out whether this bug report is related to user-mode or system-mode in Qemu. Let me break down the information given.
The issue is about configuring Qemu on Darwin/OS X where there are two versions of libtool: GNU's and Apple's. The problem arises because Apple's libtool doesn't work for building libcacard, which Qemu uses. The user is using glibtool as a workaround by setting LIBTOOL=glibtool during configure, but this variable isn't preserved when the configure script runs, causing issues.
The bug seems to involve the build process and configuration of Qemu, specifically how it handles different libtools on macOS. Since libcacard is part of Qemu's functionality, and the issue affects the compilation step, I'm thinking about where this fits in terms of user or system mode.
User-mode in Qemu refers to running guest operating systems without requiring hypervisor privileges. It's more about software emulation. System-mode involves hardware-assisted virtualization, dealing with peripherals and higher privileges.
This bug is about configuration and build tools, which are part of the development environment rather than runtime operations. Since it's a build issue related to libtool, it doesn't directly relate to running guest OSes or hardware devices. Therefore, it's more on the user side—specifically during the setup and compilation phase.
So, I think this bug falls under 'user' mode.
</think>
user
|