From: "Yu, Mingli" <mingli.yu@windriver.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-networking][PATCH] kea: replace -Og with -O
Date: Tue, 11 Jun 2019 10:50:31 +0800 [thread overview]
Message-ID: <5CFF16F7.90003@windriver.com> (raw)
In-Reply-To: <20190610133529.GA18219@localhost>
On 2019年06月10日 21:35, Adrian Bunk wrote:
> On Mon, Jun 10, 2019 at 12:13:10AM -0700, mingli.yu@windriver.com wrote:
>> From: Mingli Yu <mingli.yu@windriver.com>
>>
>> With below logic in local.conf:
>> MACHINE ??= "qemumips64"
>> MULTILIB_GLOBAL_VARIANTS_append = " libn32"
>> MULTILIBS ?= "multilib:lib32 multilib:libn32"
>> DEFAULTTUNE_virtclass-multilib-lib32 ?= "mips"
>> DEFAULTTUNE_virtclass-multilib-libn32 ?= "mips64-n32"
>> require conf/multilib.conf
>> DEBUG_BUILD = "1"
>> $ bitbake lib32-kea
>> [snip]
>> {standard input}: Assembler messages:
>> {standard input}:305030: Error: branch out of range
>> {standard input}:305041: Error: branch out of range
>> {standard input}:305432: Error: branch out of range
>> {standard input}:305443: Error: branch out of range
>> Makefile:707: recipe for target 'dhcp4_parser.lo' failed
>> make[6]: *** [dhcp4_parser.lo] Error 1
>> [snip]
>>
>> When DEBUG_BUILD enabled, -Og pass to compiler,
>> replace -Og with -O to fix the above compile error.
>> ...
>
> This sounds like a toolchain bug in gcc or binutils that should
> be fixed there.
>
> I've opened #13387 in bugzilla so that this doesn't get lost.
Could you help to post the link here about the issue you opened?
Thanks,
>
> cu
> Adrian
>
next prev parent reply other threads:[~2019-06-11 2:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-10 7:13 [meta-networking][PATCH] kea: replace -Og with -O mingli.yu
2019-06-10 13:35 ` Adrian Bunk
2019-06-11 2:50 ` Yu, Mingli [this message]
2019-06-11 21:02 ` Adrian Bunk
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=5CFF16F7.90003@windriver.com \
--to=mingli.yu@windriver.com \
--cc=bunk@stusta.de \
--cc=openembedded-devel@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