blob: f2f2b85f5efe52f5bd24af50bed88371297cc9df (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
|
<think>
Okay, so I'm trying to figure out whether this bug is related to user-mode or system-mode in QEMU based on the error message provided.
The problem occurs when compiling QEMU's commit 871af84d. The build process fails at a specific point: [3306/9698] Compiling C object libqemu...-linux-user.a.p/linux-user_syscall.c.o.
Looking at the error log, it says there's a redefinition of 'struct sched_attr'. It mentions that this structure is defined in both the application code and the host system's headers. Specifically, the file ../linux-user/syscall.c:364 is where the struct is being redefined because /usr/include/linux/sched/types.h already defines it.
Now, considering QEMU has two main modes: user-mode emulation (which runs processes without a full OS) and system-mode (emulating an entire machine with its own kernel). The error occurs in the linux-user directory, which suggests it's part of the user-mode code. Also, the inclusion chain goes through sched.h and pthread.h, which are typically used in user-space applications.
The configure command includes --enable-modules and --enable-sdl, but more importantly, the build is for the Linux user space because it mentions "linux-user". So this points to user-mode emulation.
Additionally, redefining a struct that's already part of the host's libc headers would cause compilation issues in user-mode code since QEMU's user-mode tries to emulate system calls. If both QEMU and the host include the same struct, it leads to conflicts during compilation.
So putting this together: the issue is with compiling user-mode code where a structure is redefined, which is a problem specific to how user-mode handles system call definitions.
</think>
user
|