diff options
| author | Daniel P. Berrangé <berrange@redhat.com> | 2023-01-10 12:49:01 -0500 |
|---|---|---|
| committer | Laurent Vivier <laurent@vivier.eu> | 2023-02-03 22:55:12 +0100 |
| commit | 6003159ce18faad4e1bc7bf9c85669019cd4950e (patch) | |
| tree | f77c4130cc0418638067badcb591c7fc6d23106c /meson.build | |
| parent | 9f0246539ae84a5e21efd1cc4516fc343f08115a (diff) | |
| download | qemu-6003159ce18faad4e1bc7bf9c85669019cd4950e.zip qemu-6003159ce18faad4e1bc7bf9c85669019cd4950e.tar.gz qemu-6003159ce18faad4e1bc7bf9c85669019cd4950e.tar.bz2 | |
Revert "linux-user: fix compat with glibc >= 2.36 sys/mount.h"
This reverts commit 3cd3df2a9584e6f753bb62a0028bd67124ab5532.
glibc has fixed (in 2.36.9000-40-g774058d729) the problem
that caused a clash when both sys/mount.h annd linux/mount.h
are included, and backported this to the 2.36 stable release
too:
https://sourceware.org/glibc/wiki/Release/2.36#Usage_of_.3Clinux.2Fmount.h.3E_and_.3Csys.2Fmount.h.3E
It is saner for QEMU to remove the workaround it applied for
glibc 2.36 and expect distros to ship the 2.36 maint release
with the fix. This avoids needing to add a further workaround
to QEMU to deal with the fact that linux/brtfs.h now also pulls
in linux/mount.h via linux/fs.h since Linux 6.1
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
Reviewed-by: Marc-André Lureau <marcandre.lureau@redhat.com>
Message-Id: <20230110174901.2580297-3-berrange@redhat.com>
Signed-off-by: Laurent Vivier <laurent@vivier.eu>
Diffstat (limited to 'meson.build')
| -rw-r--r-- | meson.build | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/meson.build b/meson.build index 6d3b665..cccd19f 100644 --- a/meson.build +++ b/meson.build @@ -2046,8 +2046,6 @@ config_host_data.set('HAVE_OPTRESET', cc.has_header_symbol('getopt.h', 'optreset')) config_host_data.set('HAVE_IPPROTO_MPTCP', cc.has_header_symbol('netinet/in.h', 'IPPROTO_MPTCP')) -config_host_data.set('HAVE_SYS_MOUNT_FSCONFIG', - cc.has_header_symbol('sys/mount.h', 'FSCONFIG_SET_FLAG')) # has_member config_host_data.set('HAVE_SIGEV_NOTIFY_THREAD_ID', |