| Message ID | 20220806074115.651070-1-jim@thruwave.com |
|---|---|
| State | New |
| Headers | show |
| Series | [meta-networking] networkmanager: fix iptables and nft paths | expand |
diff --git a/meta-networking/recipes-connectivity/networkmanager/networkmanager_1.38.0.bb b/meta-networking/recipes-connectivity/networkmanager/networkmanager_1.38.0.bb index c8fea5dbb..ebd25a8f8 100644 --- a/meta-networking/recipes-connectivity/networkmanager/networkmanager_1.38.0.bb +++ b/meta-networking/recipes-connectivity/networkmanager/networkmanager_1.38.0.bb @@ -55,6 +55,8 @@ EXTRA_OEMESON = "\ -Dconfig_dns_rc_manager_default=${NETWORKMANAGER_DNS_RC_MANAGER_DEFAULT} \ -Dconfig_dhcp_default=${NETWORKMANAGER_DHCP_DEFAULT} \ -Ddhcpcanon=false \ + -Diptables=${sbindir}/iptables \ + -Dnft=${sbindir}/nft \ " # stolen from https://github.com/void-linux/void-packages/blob/master/srcpkgs/NetworkManager/template
The NetworkManager meson.build is searching for iptables and nft by passing absolute paths to meson's find_program. The result is that it locates tools on the host machine when they exist at those locations. If they don't, it uses default locations. This often works out, but in some cases, such as when the host uses a merged usr scheme and the build target does not, the paths will be incorrect and the tools won't be found at runtime. These could be PACKAGECONFIG options, but since they have fallback values, completely disabling the use of either iptables or nft would require patching the meson.build or setting a bogus location. Note that this meson.build file follows the same pattern elsewhere, but most cases are already covered by PACKAGECONFIG options. Signed-off-by: Jim Broadus <jim@thruwave.com> --- .../networkmanager/networkmanager_1.38.0.bb | 2 ++ 1 file changed, 2 insertions(+)