blob: 3bcb7a8b79acfbd4e52ae42dabb9eee66907a7d3 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
|
<think>
Okay, so I'm looking at this bug report where someone is trying to run avocado tests on an aarch64 host using Ubuntu 20.04.1 LTS. The issue they're encountering is when running `make check-venv`, which is failing because it can't build the wheel for pycdlib due to an error with the 'bdist_wheel' command.
Hmm, I need to figure out whether this is a user-mode or system-mode issue. User-mode bugs typically involve applications running without special privileges and might be related to dependencies or environment setups. System-mode issues are more about hardware interactions, kernel-level stuff, devices, etc., which often require higher privileges.
Looking at the error message: the problem occurs during pip installation of pycdlib. The command fails because setuptools doesn't recognize 'bdist_wheel'. This suggests an issue with the Python environment setup. Maybe the setuptools version is too old to support that command? Or perhaps there's a missing dependency in the virtual environment.
Since this is happening within a virtual environment (as indicated by the path /home/phil/qemu/build/tests/venv), it seems like an application-level problem rather than something related to system hardware or kernel. The user is trying to run avocado tests, which are part of QEMU's test suite, so they're likely in a development setup where dependencies aren't installed correctly.
I don't see any mention of device drivers, permissions beyond the virtual environment, or system services. It's all about installing Python packages. So this should be classified as a user-mode issue because it's related to the application's environment and not the underlying operating system or hardware.
</think>
user
|