| Message ID | 20240429163859.507226-5-ross.burton@arm.com |
|---|---|
| State | New |
| Headers | show |
| Series | [v2,1/5] CI: add Kas schema comments | expand |
diff --git a/ci/external-gccarm.yml b/ci/external-gccarm.yml index 9c1eba9d..8985a1ba 100644 --- a/ci/external-gccarm.yml +++ b/ci/external-gccarm.yml @@ -8,3 +8,6 @@ local_conf_header: SKIP_RECIPE[gcc-cross-arm] = "Using external toolchain" TCMODE = "external-arm" EXTERNAL_TOOLCHAIN = "${TOPDIR}/toolchains/${TARGET_ARCH}" + # Disable ptest as this pulls target compilers, which don't + # work with external toolchain currently + DISTRO_FEATURES:remove = "ptest"
We recently switched the CI to not disable ptest, but this breaks builds that use the GCC binaries built by Arm (external-arm-toolchain). This is because the external-arm-toolchain recipe can't build packages for the target, and the standard oe-core gcc recipes assume that they're being built with themselves and make assumptions, specifically that libunwind was enabled and headers can be copied directly from the sysroot. This is a bigger problem that should be solved somehow, but for now we can just remove ptest in the external-gccarm CI jobs which removes gcc from the builds (it comes in via elfutils-ptest RDEPENDS). Signed-off-by: Ross Burton <ross.burton@arm.com> --- ci/external-gccarm.yml | 3 +++ 1 file changed, 3 insertions(+)