summaryrefslogtreecommitdiff
path: root/meson.build
Commit message (Collapse)AuthorAgeFilesLines
* Post-release version bump to 9.4.0Jiri Denemark2023-05-021-1/+1
| | | | Signed-off-by: Jiri Denemark <jdenemar@redhat.com>
* meson: Check header usabilityv9.3.0-rc2Andrea Bolognani2023-04-271-8/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This fixes cross-building in some scenarios. Specifically, when building for armv7l on x86_64, has_header() will see the x86_64 version of the linux/kmv.h header and consider it to be usable. Later, when an attempt is made to actually include it, the compiler will quickly realize that things can't quite work. The reason why we haven't hit this in our CI is that we only ever install the foreign version of header files. When building the Debian package, however, some of the Debian-specific tooling will bring in the native version of the Linux headers in addition to the foreign one, causing meson to misreport the header's availability status. Checking for actual usability, as opposed to mere presence, of headers is enough to make things work correctly in all cases. The meson documentation recommends using has_header() instead of check_header() whenever possible for performance reasons, but while testing this change on fairly old and underpowered hardware I haven't been able to measure any meaningful slowdown. https://bugs.debian.org/1024504 Suggested-by: Helmut Grohne <helmut@subdivi.de> Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Michal Privoznik <mprivozn@redhat.com>
* meson: Work around configure_file(copy:true) deprecationMichal Privoznik2023-04-201-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In our meson scripts, we use configure_file(copy:true) to copy files from srcdir into builddir. However, as of meson-0.64.0, this is deprecated [1] in favor of using: fs = import('fs') fs.copyfile(in, out) Except, the submodule's new method wasn't introduced until 0.64.0. And since we can't bump the minimal meson version we require, we have to work with both: new and old versions. Now, the fun part: fs.copyfile() is not a drop in replacement as it returns different type (a custom_target object). This is incompatible with places where we store the configure_file() retval in a variable to process it further. While we could just replace 'copy:true' with a dummy 'configuration:...' (say 'configuration: configmake_conf') we can't do that for binary files (like src/fonts/ or src/images/). Therefore, places where we are not interested in the retval can be switched to fs.copyfile() and places where we are interested in the retval will just use a dummy 'configuration:'. Except, src/network/meson.build. In here we not just copy the file but also specify alternative install dir and that's not something that fs.copyfile() can handle. Yet, using 'copy: true' is viewed wrong [2]. 1: https://mesonbuild.com/Release-notes-for-0-64-0.html#fscopyfile-to-replace-configure_filecopy-true 2: https://github.com/mesonbuild/meson/pull/10042 Signed-off-by: Michal Privoznik <mprivozn@redhat.com> Reviewed-by: Martin Kletzander <mkletzan@redhat.com>
* Move src/keycodemapdb -> subprojects/keycodemapdbMarc-André Lureau2023-04-171-0/+1
| | | | | | | | Follow better meson build system conventions. This allows to find keymap-gen or CSV without explicitly setting the paths. Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com> Reviewed-by: Michal Privoznik <mprivozn@redhat.com>
* meson: don't look for unix paths on win32Marc-André Lureau2023-04-171-5/+9
| | | | | | | | Or meson will complain with: ../meson.build:770:2: ERROR: Search directory /sbin is not an absolute path. Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com> Reviewed-by: Michal Privoznik <mprivozn@redhat.com>
* Post-release version bump to 9.3.0Jiri Denemark2023-04-011-1/+1
| | | | Signed-off-by: Jiri Denemark <jdenemar@redhat.com>
* meson: Don't build tests when CLang lacks -fsemantic-interpositionMichal Privoznik2023-03-241-2/+12
| | | | | | | | | | | There are some CLang versions that do not support -fsemantic-interposition. If that's the case, the code is optimized so much that our mocking no longer works. Therefore, disable tests and produce a warning. Signed-off-by: Michal Privoznik <mprivozn@redhat.com> Reviewed-by: Martin Kletzander <mkletzan@redhat.com>
* meson: Stop detecting -Wl,--version-script=Michal Privoznik2023-03-211-6/+1
| | | | | | | | | | | | | | | | | | | | | | With its version 16.0, the LLVM's linker turned on --no-undefined-version by default [1]. This breaks how we detect --version-script= detection, because at the compile time there's no library built yet that we can use to make --version-script= happy. Unfortunately, meson does not provide a way to detect this either [2]. But there's not much sense in detecting the argument either. We already special case some systems (windows, darwin) and do the check for others, which are expected to support versioned symbols, because of ELF. Worst case scenario - the error is reported during compile time rather than configure time. 1: https://reviews.llvm.org/D135402 2: https://github.com/mesonbuild/meson/issues/3047 Resolves: https://bugs.gentoo.org/902211 Signed-off-by: Michal Privoznik <mprivozn@redhat.com> Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
* meson: stop CLang doing inter-procedural analysisDaniel P. Berrangé2023-03-171-0/+20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The virNumaNodeIsAvailable function is stubbed out when building without libnuma, such that it just returns a constant value. When CLang is optimizing, it does inter-procedural analysis across function calls. When it sees that the call to virNumaNodeIsAvailable returns a fixed constant, it elides the conditional check for errors in the callers such as virNumaNodesetIsAvailable. This is a valid optimization as the C standard declares that there must only be one implementation of each function in a binary. This is normally the case, but ELF allows for function overrides when linking or at runtime with LD_PRELOAD, which is technically outside the mandated C language behaviour. So while CLang's optimization works fine at runtime, it breaks in our test suite which aims to mock the virNumaNodeIsAvailable function so that it has specific semantics regardless of whether libnuma is built or not. The return value check optimization though means our mock override won't have the right effect. The mock will be invoked, but its return value is not used. Potentially the same problem could be exhibited with GCC if certain combinations of optimizations are enabled, though thus far we've not seen it. To be robust on both CLang and GCC we need to make it more explicit that we want to be able to replace functions and thus optimization of calls must be limited. Currently we rely on 'noinline' which does successfully prevent inlining of the function, but it cannot stop the eliding of checks based on the constant return value. Thus we need a bigger hammer. There are a couple of options to disable this optimization: * Annotate a symbol as 'weak'. This is tells the compiler that the symbol is intended to be overridable at linktime or runtime, and thus it will avoid doing inter-procedural analysis for optimizations. This was tried previously but have to be reverted as it had unintended consequences when linking .a files into our final .so, resulting in all the weak symbol impls being lost. See commit 407a281a8e2b6c5078ba1148535663ea64fd9314 * Annotate a symbol with 'noipa'. This tells the compiler to avoid inter-procedural analysis for calls to just this function. This would be ideal match for our scenario, but unfortunately it is only implemented for GCC currently: https://reviews.llvm.org/D101011 * The '-fsemantic-interposition' argument tells the optimizer that any functions may be replaced with alternative implementations that have different semantics. It thus blocks any optimizations across function calls. This is quite a harsh block on the optimizer, but it appears to be the only one that is viable with CLang. Out of those choices option (3) is the only viable option for CLang. We don't want todo it for GCC though as it is such a big hammer. Probably we should apply (2) for GCC, should we experiance a problem in future. Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
* Post-release version bump to 9.2.0Jiri Denemark2023-03-011-1/+1
| | | | Signed-off-by: Jiri Denemark <jdenemar@redhat.com>
* Post-release version bump to 9.1.0Jiri Denemark2023-01-161-1/+1
| | | | Signed-off-by: Jiri Denemark <jdenemar@redhat.com>
* qemu: hook up passt config to qemu domainsLaine Stump2023-01-101-0/+1
| | | | | | | | | | | | | This consists of (1) adding the necessary args to the qemu commandline netdev option, and (2) starting a passt process prior to starting qemu, and making sure that it is terminated when it's no longer needed. Under normal circumstances, passt will terminate itself as soon as qemu closes its socket, but in case of some error where qemu is never started, or fails to startup completely, we need to terminate passt manually. Signed-off-by: Laine Stump <laine@redhat.com> Reviewed-by: Ján Tomko <jtomko@redhat.com>
* virnuma: Allow multiple nodes for preferred policyMichal Privoznik2022-12-141-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | In the past, the preferred policy (VIR_DOMAIN_NUMATUNE_MEM_PREFERRED) required exactly one (host) NUMA node. This made sense because: 1) the libnuma API - numa_set_preferred() allowed exactly one node, because 2) corresponding kernel syscall (__NR_set_mempolicy) accepted exactly one node (for MPOL_PREFERRED mode). But things have changed since then. Firstly, kernel introduced new MPOL_PREFERRED_MANY mode (v5.15-rc1~107^2~21) which was then exposed in libnuma as numa_set_preferred_many() (v2.0.15~24). Fortunately, libnuma also exposes numa_has_preferred_many() which returns whether the kernel has support for the new mode (1) or not (0). Putting this all together, we can lift our check for sufficiently new kernel and libnuma. Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=2151064 Signed-off-by: Michal Privoznik <mprivozn@redhat.com> Reviewed-by: Ján Tomko <jtomko@redhat.com>
* util: implement secure erase with explicit_bzeroDaniel P. Berrangé2022-12-131-0/+1
| | | | | | | This is available on at least FreeBSD and GLibc >= 2.25. Reviewed-by: Ján Tomko <jtomko@redhat.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
* meson: Provide default values for nonexistent xenlight pkgconfig varsMichal Privoznik2022-12-121-2/+2
| | | | | | | | | | | | | | It may happen that xenlight pkgconfig file does not contain 'xenfirmwaredir' and/or 'libexec_bin' variables, which is okay and we have code that deals with this situation. But that code is executed when the queried value is an empty string. This may not always be the case and we should specifically set 'default_value' so that the empty string is returned if pkgconfig variable doesn't exist. Fixes: 968479adcfa5c49b29b7b6680dcaffde1408f044 Signed-off-by: Michal Privoznik <mprivozn@redhat.com> Reviewed-by: Martin Kletzander <mkletzan@redhat.com>
* meson: remove obsolete check for BPF_CGROUP_DEVICEDaniel P. Berrangé2022-12-121-7/+0
| | | | | | | | | | | | | | | | The BPF_CGROUP_DEVICE constant was introduced to Linux in commit ebc614f687369f9df99828572b1d85a7c2de3d92 Author: Roman Gushchin <roman.gushchin@linux.dev> Date: Sun Nov 5 08:15:32 2017 -0500 bpf, cgroup: implement eBPF-based device controller for cgroup v2 This is old enough that all our supported platforms can be assumed to have this feature. Reviewed-by: Ján Tomko <jtomko@redhat.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
* meson: remove obsolete check for BPF_PROG_QUERYDaniel P. Berrangé2022-12-121-1/+0
| | | | | | | | | | | | | | | | The BPF_PROG_QUERY constant was introduced to Linux in commit defd9c476fa6b01b4eb5450452bfd202138decb7 Author: Alexei Starovoitov <ast@kernel.org> Date: Mon Oct 2 22:50:26 2017 -0700 libbpf: sync bpf.h This is old enough that all our supported platforms can be assumed to have this feature. Reviewed-by: Ján Tomko <jtomko@redhat.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
* meson: remove obsolete check for VHOST_VSOCK_SET_GUEST_CIDDaniel P. Berrangé2022-12-121-3/+0
| | | | | | | | | | | | | | | | The VHOST_VSOCK_SET_GUEST_CID constant was introduced to Linux in commit 433fc58e6bf2c8bd97e57153ed28e64fd78207b8 Author: Asias He <asias@redhat.com> Date: Thu Jul 28 15:36:34 2016 +0100 VSOCK: Introduce vhost_vsock.ko This is old enough that all our supported platforms can be assumed to have this feature. Reviewed-by: Ján Tomko <jtomko@redhat.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
* meson: remove obsolete check for linux/magic.hDaniel P. Berrangé2022-12-121-1/+0
| | | | | | | | | | | | | | | | The linux/magic.h header has existed since commit e18fa700c9a31360bc8f193aa543b7ef7b39a06b Author: Jeff Garzik <jeff@garzik.org> Date: Sun Sep 24 11:13:19 2006 -0400 Move several *_SUPER_MAGIC symbols to include/linux/magic.h. This is old enough that all our supported platforms can be assumed to have this header. Reviewed-by: Ján Tomko <jtomko@redhat.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
* meson: remove obsolete check for DEVLINK_CMD_ESWITCH_GETDaniel P. Berrangé2022-12-121-11/+0
| | | | | | | | | | | | | | | | The DEVLINK_CMD_ESWITCH_GET constant was introduced to Linux in commit adf200f31c000d707e4afe238ed1d1199e0cce7c Author: Jiri Pirko <jiri@mellanox.com> Date: Thu Feb 9 15:54:33 2017 +0100 devlink: fix the name of eswitch commands This is old enough that all our supported platforms can be assumed to have this feature. Reviewed-by: Ján Tomko <jtomko@redhat.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
* meson: simplify check for virnetdevbridge.c headersDaniel P. Berrangé2022-12-121-12/+4
| | | | | | | | | | The headers required by virnetdevbridge.c have all exited since before Linux moved to git. It is sufficient to check for just one of them in order to give an error message about needing kernel headers installed. Reviewed-by: Ján Tomko <jtomko@redhat.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
* meson: remove obsolete check for GET_VLAN_VID_CMDDaniel P. Berrangé2022-12-121-3/+0
| | | | | | | | | | | The GET_VLAN_VID_CMD constant has existed since before Linux moved to git. This is old enough that all our supported platforms can be assumed to have this feature. Reviewed-by: Ján Tomko <jtomko@redhat.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
* meson: remove obsolete check for ETHTOOL_GCOALESCEDaniel P. Berrangé2022-12-121-3/+0
| | | | | | | | | | | The ETHTOOL_GCOALESCE constant has existed since before Linux moved to git. This is old enough that all our supported platforms can be assumed to have this feature. Reviewed-by: Ján Tomko <jtomko@redhat.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
* meson: remove obsolete check for ETHTOOL_GFEATURESDaniel P. Berrangé2022-12-121-1/+0
| | | | | | | | | | | | | | | | The ETHTOOL_GFEATURES constant was introduced to Linux in commit 5455c6998d34dc983a8693500e4dffefc3682dc5 Author: Michał Mirosław <mirq-linux@rere.qmqm.pl> Date: Tue Feb 15 16:59:17 2011 +0000 net: Introduce new feature setting ops This is old enough that all our supported platforms can be assumed to have this feature. Reviewed-by: Ján Tomko <jtomko@redhat.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
* meson: remove obsolete check for ETH_FLAG_RXHASHDaniel P. Berrangé2022-12-121-1/+0
| | | | | | | | | | | | | | | | The ETH_FLAG_RXHASH constant was introduced to Linux in commit b00fabb4020d17bda4bea59507e09fadf573088d Author: stephen hemminger <shemminger@vyatta.com> Date: Mon Mar 29 14:47:27 2010 +0000 netdev: ethtool RXHASH flag This is old enough that all our supported platforms can be assumed to have this feature. Reviewed-by: Ján Tomko <jtomko@redhat.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
* meson: remove obsolete check for ETH_FLAG_NTUPLEDaniel P. Berrangé2022-12-121-1/+0
| | | | | | | | | | | | | | | | | | | | The ETH_FLAG_NTUPLE constant was introduced to Linux in commit 15682bc488d4af8c9bb998844a94281025e0a333 Author: Peter P Waskiewicz Jr <peter.p.waskiewicz.jr@intel.com> Date: Wed Feb 10 20:03:05 2010 -0800 ethtool: Introduce n-tuple filter programming support This is old enough that all our supported platforms can be assumed to have this feature. A typo in the existing condition "NTUBLE" instead of "NTUPLE" meant the code was never enabled in the first place, which is an illustration of why it is worth eliminating redundant conditional checks. Reviewed-by: Ján Tomko <jtomko@redhat.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
* meson: remove obsolete check for ETH_FLAG_TXVLAN/RXVLANDaniel P. Berrangé2022-12-121-1/+0
| | | | | | | | | | | | | | | | The ETH_FLAG_TXVLAN/RXVLAN constants were introduced to Linux in commit d5dbda23804156ae6f35025ade5307a49d1db6d7 Author: Jesse Gross <jesse@nicira.com> Date: Wed Oct 20 13:56:07 2010 +0000 ethtool: Add support for vlan accleration. This is old enough that all our supported platforms can be assumed to have this feature. Reviewed-by: Ján Tomko <jtomko@redhat.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
* meson: remove obsolete check for ETH_FLAG_LRODaniel P. Berrangé2022-12-121-1/+0
| | | | | | | | | | | | | | | | The ETH_FLAG_LRO constant was introduced to Linux in commit 3ae7c0b2e3747b50c3a6c63ebb67469e0a6b3203 Author: Jeff Garzik <jeff@garzik.org> Date: Wed Aug 15 16:00:51 2007 -0700 [ETHTOOL]: Add ETHTOOL_[GS]FLAGS sub-ioctls This is old enough that all our supported platforms can be assumed to have this feature. Reviewed-by: Ján Tomko <jtomko@redhat.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
* meson: remove obsolete check for ETHTOOL_GFLAGSDaniel P. Berrangé2022-12-121-1/+0
| | | | | | | | | | | | | | | | The ETHTOOL_GFLAGS constant was introduced to Linux in commit 3ae7c0b2e3747b50c3a6c63ebb67469e0a6b3203 Author: Jeff Garzik <jeff@garzik.org> Date: Wed Aug 15 16:00:51 2007 -0700 [ETHTOOL]: Add ETHTOOL_[GS]FLAGS sub-ioctls This is old enough that all our supported platforms can be assumed to have this feature. Reviewed-by: Ján Tomko <jtomko@redhat.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
* meson: remove obsolete check for ETHTOOL_GGRODaniel P. Berrangé2022-12-121-1/+0
| | | | | | | | | | | | | | | | The ETHTOOL_GGRO constant was introduced to Linux in commit b240a0e5644eb817c4a397098a40e1ad42a615bc Author: Herbert Xu <herbert@gondor.apana.org.au> Date: Mon Dec 15 23:44:31 2008 -0800 ethtool: Add GGRO and SGRO ops This is old enough that all our supported platforms can be assumed to have this feature. Reviewed-by: Ján Tomko <jtomko@redhat.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
* meson: remove obsolete check for ETHTOOL_GGSODaniel P. Berrangé2022-12-121-1/+0
| | | | | | | | | | | | | | | | The ETHTOOL_GGSO constant was introduced to Linux in commit 37c3185a02d4b85fbe134bf5204535405dd2c957 Author: Herbert Xu <herbert@gondor.apana.org.au> Date: Thu Jun 22 03:07:29 2006 -0700 [NET]: Added GSO toggle This is old enough that all our supported platforms can be assumed to have this feature. Reviewed-by: Ján Tomko <jtomko@redhat.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
* meson: drop check for unshare()Daniel P. Berrangé2022-12-121-14/+1
| | | | | | | | | | | | | | | | | The unshare() syscall was introduced to Linux in commit 2da436e00f9a5fdd0fb6b31e4b2b2ba82e8f5ab8 Author: JANAK DESAI <janak@us.ibm.com> Date: Tue Feb 7 12:59:03 2006 -0800 [PATCH] unshare system call -v5: system call registration for i386 This is old enough that all our supported platforms can be assumed to have this feature. Furthermore, the virprocess.c file was already using unshare() with nothing more than a #ifdef __linux__ check. Reviewed-by: Ján Tomko <jtomko@redhat.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
* meson: remove obsolete check for LO_FLAGS_AUTOCLEARDaniel P. Berrangé2022-12-121-2/+1
| | | | | | | | | | | | | | | | | | The LO_FLAGS_AUTOCLEAR constant was introduced to Linux in commit 96c5865559cee0f9cbc5173f3c949f6ce3525581 Author: David Woodhouse <dwmw2@infradead.org> Date: Wed Feb 6 01:36:27 2008 -0800 Allow auto-destruction of loop devices This is old enough that all our supported platforms can be assumed to have this feature. For added fun this whole meson check was semantically insane because EPOLL_CLOEXEC is not a valid arg to unshare(). Reviewed-by: Ján Tomko <jtomko@redhat.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
* meson: remove obsolete check for EPOLL_CLOEXECDaniel P. Berrangé2022-12-121-1/+1
| | | | | | | | | | | | | | | | | | The EPOLL_CLOEXEC constant was introduced to Linux in commit a0998b50c3f0b8fdd265c63e0032f86ebe377dbf Author: Ulrich Drepper <drepper@redhat.com> Date: Wed Jul 23 21:29:27 2008 -0700 flag parameters: epoll_create This is old enough that all our supported platforms can be assumed to have this feature. For added fun this whole meson check was semantically insane because EPOLL_CLOEXEC is not a valid arg to unshare(). Reviewed-by: Ján Tomko <jtomko@redhat.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
* meson: remove obsolete check for LOOP_CTL_GET_FREEDaniel P. Berrangé2022-12-121-13/+0
| | | | | | | | | | | | | | | | | | | | | | The LOOP_CTL_GET_FREE constant was introduced to Linux in commit 770fe30a46a12b6fb6b63fbe1737654d28e84844 Author: Kay Sievers <kay.sievers@vrfy.org> Date: Sun Jul 31 22:08:04 2011 +0200 loop: add management interface for on-demand device allocation This is old enough that all our supported platforms can be assumed to have this feature. As a plus point, this meson check is going to start failing with future GCC. It fails to set _GNU_SOURCE, thus 'unshare' is not defined by the header, and its relying on an implicit function decl. For added fun this whole meson check was semantically insane because LOOP_CTL_GET_FREE is not a valid arg to unshare(). Fixes https://fedoraproject.org/wiki/Toolchain/PortingToModernC Reviewed-by: Ján Tomko <jtomko@redhat.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
* Post-release version bump to 9.0.0Jiri Denemark2022-12-011-1/+1
| | | | Signed-off-by: Jiri Denemark <jdenemar@redhat.com>
* Post-release version bump to 8.10.0Jiri Denemark2022-11-011-1/+1
| | | | Signed-off-by: Jiri Denemark <jdenemar@redhat.com>
* meson: Bump minimal required meson versionMichal Privoznik2022-10-101-1/+1
| | | | | | | | Bump the minimal required version to 0.56.0. Looking into our CI this is the oldest version we install. Signed-off-by: Michal Privoznik <mprivozn@redhat.com> Reviewed-by: Ján Tomko <jtomko@redhat.com>
* Replace dep.get_pkgconfig_variable() with dep.get_variable(pkgconfig:)Michal Privoznik2022-10-101-7/+7
| | | | | | | | The get_pkgconfig_variable() method is deprecated in 0.56.0 and we're recommended to use get_variable(pkgconfig : ...) instead. Signed-off-by: Michal Privoznik <mprivozn@redhat.com> Reviewed-by: Ján Tomko <jtomko@redhat.com>
* meson: Replace external_program.path() with external_program.full_path()Michal Privoznik2022-10-101-18/+18
| | | | | | | | | The path() method is deprecated in 0.55.0 and we're recommended to use full_path() instead. Interestingly, we were already doing do in couple of places, but not all of them. Signed-off-by: Michal Privoznik <mprivozn@redhat.com> Reviewed-by: Ján Tomko <jtomko@redhat.com>
* meson: Replace meson.source_root() with meson.project_source_root()Michal Privoznik2022-10-101-2/+2
| | | | | | | | The source_root() method is deprecated in 0.56.0 and we're recommended to use project_source_root() instead. Signed-off-by: Michal Privoznik <mprivozn@redhat.com> Reviewed-by: Ján Tomko <jtomko@redhat.com>
* meson: Replace meson.build_root() with meson.project_build_root()Michal Privoznik2022-10-101-4/+4
| | | | | | | | The build_root() method is deprecated in 0.56.0 and we're recommended to use project_build_root() instead. Signed-off-by: Michal Privoznik <mprivozn@redhat.com> Reviewed-by: Ján Tomko <jtomko@redhat.com>
* Post-release version bump to 8.9.0Jiri Denemark2022-10-031-1/+1
| | | | Signed-off-by: Jiri Denemark <jdenemar@redhat.com>
* meson: Require libssh-0.8.1 or newerMichal Privoznik2022-09-201-14/+1
| | | | | | | | | | | | | | | | | | | According to repology.org: RHEL-8: 0.9.4 RHEL-9: 0.9.6 Debian 11: 0.9.5 openSUSE Leap 15.3: 0.8.7 Ubuntu 20.04: 0.9.3 And the rest of distros has something newer anyways. Requiring 0.8.1 or newer allows us to drop the terrible hack where we rename functions at meson level using #define. Note, 0.8.0 is the version of libssh where the rename happened. It also allows us to stick with SHA-256 hash algorithm for public keys. Signed-off-by: Michal Privoznik <mprivozn@redhat.com> Reviewed-by: Ján Tomko <jtomko@redhat.com>
* Revert "build: Decrease maximum stack frame size to 2048"Peter Krempa2022-09-091-1/+1
| | | | | | | | | | | | The bhyve driver still has some frames larger than 2048 bytes, so we need to keep the limit as is. The CI failure was masked by the Freebsd-13 failing for unrelated reasons. This reverts commit 46302172d47709b169c4b9b4cd6a4847fc2f0b4c Signed-off-by: Peter Krempa <pkrempa@redhat.com>
* build: Decrease maximum stack frame size to 2048Peter Krempa2022-09-091-1/+1
| | | | | | | | After recent cleanups we can now restrict the maximum stack frame size to 2k. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Ján Tomko <jtomko@redhat.com>
* Remove support for building the sheepdog storage driver backendPeter Krempa2022-09-011-11/+0
| | | | | | | | | | | | The sheepdog project is unmaintained, with last commit in 2018 and numerous unanswered issues reported. Remove the libvirt storage driver support for it to follow the removal of the client support in qemu. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Claudio Fontana <cfontana@suse.de> Reviewed-by: Ján Tomko <jtomko@redhat.com>
* Post-release version bump to 8.8.0Jiri Denemark2022-09-011-1/+1
| | | | Signed-off-by: Jiri Denemark <jdenemar@redhat.com>
* rpm: merge mingw sub-packages into native specDaniel P. Berrangé2022-08-091-12/+5
| | | | | | | | | | | | One specfile containing both native and mingw builds is the new best practice for Fedora. This reduces the maint burden and ensures the mingw packages don't fall behind. Note this adds many more BuildRequires for anyone building on Fedora, which will now need installing. Reviewed-by: Pavel Hrdina <phrdina@redhat.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
* Post-release version bump to 8.7.0Jiri Denemark2022-08-011-1/+1
| | | | Signed-off-by: Jiri Denemark <jdenemar@redhat.com>
View Lorry Controller Status