13571 2019-10-04 00:26:16 +0000 Meson cross detection is broken 2019-10-17 14:54:07 +0000 1 1 7 Build System, Metadata & Runtime OE-Core devtools / tool chain unspecified x86 Multiple RESOLVED FIXED Medium+ normal 2.8 M4 1 ross.burton ross.burton meta.mr.watcher meta.watcher --- --- No (bug/feature does not impact docs) oldest_to_newest 85206 0 ross.burton 2019-10-04 00:26:16 +0000 Upstream Meson fails to detect cross if host and target are compatible (x86->x86). We patch Meson to check if an exe_wrapper is needed instead (0001-mesonbuild-environment.py-do-not-determine-whether-a.patch). This appears to work for cross builds but the same patch breaks builds on target where it believes that an exe wrapper is needed and believes that a native build is cross. I've filed https://github.com/mesonbuild/meson/issues/5993 upstream to track this but we need to fix this for M4 I think. 85211 1 alex.kanavin 2019-10-04 09:26:52 +0000 How can I reproduce this? 85212 2 alex.kanavin 2019-10-04 09:29:53 +0000 Maybe we can simply apply this patch only for native and nativesdk but not for target? Meanwhile hopefully upstream will sort this out. 85243 3 ross.burton 2019-10-07 09:46:22 +0000 The reproducer is to try a build on target using Meson: it will detect as cross due to the change in 0001-mesonbuild-environment.py-do-not-determine-whether-a.patch. Removing the patch will break cross builds if the machines match. I've a patch which does this: def is_cross_build(self) -> bool: - return self.need_exe_wrapper() + return bool(self.coredata.cross_files) Appears to work. 85244 4 ross.burton 2019-10-07 09:51:34 +0000 Good news is that over the weekend Jussi merged a fix upstream. 85370 5 ross.burton 2019-10-17 14:54:07 +0000 Fixed in oe-core 9aa543aa9bd78c63343ae28fc85113ca2c9e0094.