1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
|
<think>
Okay, I need to classify this bug report into one of the given categories for QEMU. Let me start by reading through the problem description carefully.
The user mentioned that they're having a compilation failure with libfdt.a. They checked out dtc on October 28th and tried compiling again tonight. The issue occurs at line 234 in the Makefile of qemu/dtc/. They inserted a strace command to capture the error but found it inconclusive.
The specific error message is "/usr/bin/ar: deux operations différentes spécifiées," which translates to "two different operations specified." This suggests there's an issue with how the archiver (ar) is being used during the build process.
Looking at their environment, they're using Arch Linux with binutils 2.23.2 and gcc 4.8.2. The kernel is kvm-3.12.0-rc5 from git. So, it's a setup involving KVM and QEMU.
Now, I need to map this issue to the provided categories: mistranslation, assembly lowering, other, device, graphic, socket, network, KVM, boot, vnc, debug, files, permissions, performance, kernel, peripherals, hypervisor.
The problem seems related to the build process and specifically with the archiver command (ar). The error message points to an issue with how ar is being called—two different operations specified. This could mean that in the Makefile, perhaps there's a typo or incorrect usage of ar commands leading to conflicting operations.
Looking at the categories, "files" might be relevant here since it's related to file handling during compilation. However, "KVM" and "hypervisor" are more about the virtualization aspects, which don't directly apply here. The issue isn't with user-mode translation or assembly lowering, so mistranslation or assembly aren't fits.
The problem is in the build process, specifically with libfdt.a and the Makefile. Since it's a compilation error during library creation, "files" seems appropriate as it relates to file operations and build artifacts.
</think>
files
|