In file included from /usr/include/linux/btrfs.h:29,
from ../linux-user/syscall.c:163:
/usr/include/linux/fs.h:50:8: error: redefinition of 'struct file_clone_range'
50 | struct file_clone_range {
| ^~~~~~~~~~~~~~~~
../linux-user/syscall.c:129:8: note: originally defined here
129 | struct file_clone_range {
| ^~~~~~~~~~~~~~~~
was caused by btrfs.h gaining an include of linux/fs.h,
which clashed with QEMU's workaround for glibc compat
with linux/mount.h. GLibc huas fixed their sys/mount.h
so we can drop the QEMU workaround, thus fixing the
btrfs.h problem.
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
This files does not exist on riscv64 architecture:
[..]
Processing files: qemu-user-static-riscv-7.0.0-6.1.riscv64.fc33.riscv64
error: File not found: /builddir/build/BUILDROOT/qemu-7.0.0-6.1.riscv64.fc33.riscv64/usr/lib/binfmt.d/qemu-riscv32-static.conf
RPM build errors:
File not found: /builddir/build/BUILDROOT/qemu-7.0.0-6.1.riscv64.fc33.riscv64/usr/lib/binfmt.d/qemu-riscv32-static.conf
Child return code was: 1
EXCEPTION: [Error()]
Signed-off-by: David Abdurachmanov <davidlt@rivosinc.com>
This was tested on multiple boards with the latest stable kernel v5.18.8
and with two glibc version (incl. not yet released 2.36) with the same
result.
qtests hang on a couple exotic arches (e.g. hppa).
Signed-off-by: David Abdurachmanov <davidlt@rivosinc.com>
pipewire-jack-audio-connection-kit is a drop in replacement
for jack-audio-connection-kit, but they have package conflicts.
The former is pulled in by default for Fedora Workstation, so prefer
its matching -devel variant, so `dnf builddep` has a chance to work
and not error due to the conflict.
Signed-off-by: Cole Robinson <crobinso@redhat.com>
This was added over 12 years ago, in my testing it seem to be
required. Seems s390x builders only advertise -j2 anyways
Signed-off-by: Cole Robinson <crobinso@redhat.com>
When we split virtiofsd out from qemu-common, the intention was it
would be installed with `qemu-system-XXX` but not
`qemu-system-XXX-core`, similar to how device modules are treated.
It was accidentally added to the `qemu` metapackage, which is rarely
used.
This fixes that mistake.
https://bugzilla.redhat.com/show_bug.cgi?id=2083155
Signed-off-by: Cole Robinson <crobinso@redhat.com>
qemu-common has a dep on python, and has nothing that is critical for
the operation of the userspace emulators. At most the qemu-trace-stap
tool is useful, but we shouldn't force install of qemu-common just for
that. qemu-user-static needs to be lightweight as its used to support
cross-arch execution in scenarios where container/image size matters.
In dropping qemu-common as a dep, we just need to ensure we still have
the license files present.
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
The static build of QEMU installs a copy of 'qemu-trace-stap' python
script, which gets renamed to 'qemu-trace-stap-static' by an overly
enthusiastic wildcard. This ends up adding a python dependency to
the qemu-user-static RPM, which is unhelpful.
Anyone who wants to trace QEMU user binaries with the stap helper
can easily install qemu-common as desired.
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
Pulled in by qemu-* but not qemu-*-core, like we do for device modules.
There's a virtual Provides: vhostuser-backend(fs) indicating this
packages is a vhost-user.json fs provider.
Use that for the qemu dep, as in the future there will be alternate
virtiofsd impl packages in Fedora
Signed-off-by: Cole Robinson <crobinso@redhat.com>
