From: "Bernhard Rosenkränzer" <bernhard.rosenkraenzer.ext@huawei.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] gcc: upgrade 11.2 -> current 12 snapshot
Date: Thu, 07 Apr 2022 06:29:14 -0700 [thread overview]
Message-ID: <23864.1649338154287208609@lists.openembedded.org> (raw)
In-Reply-To: <ab842b2db53d29b11298382f7c94b8ef903ea1f1.camel@linuxfoundation.org>
[-- Attachment #1: Type: text/plain, Size: 1712 bytes --]
On Thu, Apr 7, 2022 at 02:32 PM, Richard Purdie wrote:
>
> On Thu, 2022-04-07 at 14:26 +0200, Bernhard Rosenkränzer via
> lists.openembedded.org wrote:
>
>> rename from meta/recipes-devtools/gcc/gcc-cross-canadian_11.2.bb
>> rename to meta/recipes-devtools/gcc/gcc-cross-canadian_12.0.bb
>> diff --git a/meta/recipes-devtools/gcc/gcc-cross.inc
>> b/meta/recipes-devtools/gcc/gcc-cross.inc
>> index 3ffa1f0c46..0e8119384b 100644
>> --- a/meta/recipes-devtools/gcc/gcc-cross.inc
>> +++ b/meta/recipes-devtools/gcc/gcc-cross.inc
>> @@ -47,6 +47,15 @@ ARCH_FLAGS_FOR_TARGET +=
>> "-isystem${STAGING_DIR_TARGET}${target_includedir}"
>> do_configure:prepend () {
>> install -d ${RECIPE_SYSROOT}${target_includedir}
>> touch ${RECIPE_SYSROOT}${target_includedir}/limits.h
>> +
>> + if ! echo ${@d.getVar("TARGET_OS")} | grep -qi linux; then
>> + # Building Zephyr with DWARF-5 is problematic because
>> + # its kernel tests use pyelftools, which has incomplete
>> + # DWARF-5 support (even after applying preliminary
>> + # support patches). Use DWARF-4 on Zephyr and FreeRTOS
>> + # for the time being.
>> + sed -i -e 's,Var(dwarf_version) Init(5),Var(dwarf_version) Init(4),'
>> ${S}/gcc/common.opt
>> + fi
>> }
>>
>> do_compile () {
>
> Unfortunately you can't do that. The gcc-cross is shared amongst all
> targets on
> a given architecture. This will "kind of work" in that other sstate code
> will
> clean it up and rebuild gcc but it isn't as designed and can't merge like
> that
> I'm afraid.
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.
ttyl
bero
[-- Attachment #2: Type: text/html, Size: 1775 bytes --]
next prev parent reply other threads:[~2022-04-07 15:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-07 12:26 [PATCH] gcc: upgrade 11.2 -> current 12 snapshot Bernhard Rosenkränzer
2022-04-07 12:32 ` [OE-core] " Richard Purdie
2022-04-07 13:29 ` Bernhard Rosenkränzer [this message]
2022-04-07 20:07 ` Khem Raj
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=23864.1649338154287208609@lists.openembedded.org \
--to=bernhard.rosenkraenzer.ext@huawei.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox