On Thu, Apr 7, 2022 at 02:32 PM, Richard Purdie wrote:<br />
<blockquote>On Thu, 2022-04-07 at 14:26 +0200, Bernhard Rosenkr&auml;nzer via<br />lists.openembedded.org wrote:<br />
<blockquote>rename from meta/recipes-devtools/gcc/gcc-cross-canadian_11.2.bb<br />rename to meta/recipes-devtools/gcc/gcc-cross-canadian_12.0.bb<br />diff --git a/meta/recipes-devtools/gcc/gcc-cross.inc b/meta/recipes-devtools/gcc/gcc-cross.inc<br />index 3ffa1f0c46..0e8119384b 100644<br />--- a/meta/recipes-devtools/gcc/gcc-cross.inc<br />+++ b/meta/recipes-devtools/gcc/gcc-cross.inc<br />@@ -47,6 +47,15 @@ ARCH_FLAGS_FOR_TARGET += "-isystem${STAGING_DIR_TARGET}${target_includedir}"<br />do_configure:prepend () {<br />install -d ${RECIPE_SYSROOT}${target_includedir}<br />touch ${RECIPE_SYSROOT}${target_includedir}/limits.h<br />+<br />+ if ! echo ${@d.getVar("TARGET_OS")} | grep -qi linux; then<br />+ # Building Zephyr with DWARF-5 is problematic because<br />+ # its kernel tests use pyelftools, which has incomplete<br />+ # DWARF-5 support (even after applying preliminary<br />+ # support patches). Use DWARF-4 on Zephyr and FreeRTOS<br />+ # for the time being.<br />+ sed -i -e 's,Var(dwarf_version) Init(5),Var(dwarf_version) Init(4),' ${S}/gcc/common.opt<br />+ fi<br />}<br /><br />do_compile () {</blockquote>
Unfortunately you can't do that. The gcc-cross is shared amongst all targets on<br />a given architecture. This will "kind of work" in that other sstate code will<br />clean it up and rebuild gcc but it isn't as designed and can't merge like that<br />I'm afraid.</blockquote>
True, didn't think of that. I've backed out this part and sent a new patch. Will address the zephyr problem with an added -gdwarf-4 flag in zephyr configs.<br /><br />ttyl<br />bero