Message ID | 20230130050909.133727-4-raj.khem@gmail.com |
---|---|
State | New |
Headers | show |
Series | [meta-networking,01/12] wireshark: Add nghttp2 packageconfig | expand |
diff --git a/meta-oe/recipes-devtools/mercurial/mercurial_6.1.bb b/meta-oe/recipes-devtools/mercurial/mercurial_6.1.bb index 3abecc3054..a415ebc1e8 100644 --- a/meta-oe/recipes-devtools/mercurial/mercurial_6.1.bb +++ b/meta-oe/recipes-devtools/mercurial/mercurial_6.1.bb @@ -7,7 +7,7 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=b234ee4d69f5fce4486a80fdaf4a4263" DEPENDS = "python3 python3-native" RDEPENDS:${PN} = "python3 python3-modules" -inherit python3native +inherit python3native python3targetconfig SRC_URI = "https://www.mercurial-scm.org/release/${BP}.tar.gz" SRC_URI[sha256sum] = "86f98645e4565a9256991dcde22b77b8e7d22ca6fbb60c1f4cdbd8469a38cc1f"
It uses python3-config during build to grok the python specific includedirs, therefore its important to ensure that target specific python3-config is used, otherwise currently it defaults to native python3-config which ends up adding native python3 include paths which might work out ok but is exposed when target is 32bit + lfs enabled, the headers don't match between native and target python Signed-off-by: Khem Raj <raj.khem@gmail.com> --- meta-oe/recipes-devtools/mercurial/mercurial_6.1.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)