https://bugzilla.suse.com/show_bug.cgi?id=1208657 Bug ID: 1208657 Summary: QEMU failing to build with kernel 6.2 due to header issues Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KVM Assignee: kvm-bugs@suse.de Reporter: dfaggioli@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- The problem is described here: https://lore.kernel.org/qemu-devel/20230110174901.2580297-1-berrange@redhat.... So, quoting from there:

It didn't appear that glibc was going to fix the problem breaking includes of linux/mount.h vs sys/mount.h, so QEMU applied a workaround copying the symbols/structs we need into a local header.

Since then Linux modified linux/btrfs.h to pull in linux/fs.h which caused a clash with our workaround. Rather than invent workarounds for our workarounds, we can luckily just drop our previous workarounds. glibc has been fixed after all, and backported this fix to the stable 2.36 release series too. We should just expect distros to pull in the stable fix, which Fedora at least has already done.

The mentioned workaround is something we included in our QEMU 7.1 package as a downstream patch (see bug 1204001). And now we're suffering the consequences described in the second paragraph. The actual error, when trying to build QEMU with kernel 6.2's headers is this one:

[ 56s] In file included from /usr/include/linux/btrfs.h:29, [ 56s] from ../linux-user/syscall.c:163: [ 56s] /usr/include/linux/fs.h:50:8: error: redefinition of 'struct file_clone_range' [ 56s] 50 | struct file_clone_range { [ 56s] | ^~~~~~~~~~~~~~~~ [ 56s] ../linux-user/syscall.c:129:8: note: originally defined here [ 56s] 129 | struct file_clone_range { [ 56s] | ^~~~~~~~~~~~~~~~

-- You are receiving this mail because: You are on the CC list for the bug.