From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/apitrace: fix apitrace microblaze build failure
Date: Mon, 22 Jun 2020 22:55:37 +0200 [thread overview]
Message-ID: <20200622225537.2d4764be@windsurf.home> (raw)
In-Reply-To: <20200610161601.290420-1-giulio.benetti@benettiengineering.com>
On Wed, 10 Jun 2020 18:16:01 +0200
Giulio Benetti <giulio.benetti@benettiengineering.com> wrote:
> Apitrace is affected by Gcc Bug 68485 that has already been worked
> around, but after version bumping, CMakeLists.txt adds -O2 to
> CMAKE_C_FLAGS_RELWITHDEBINFO that is in order appended to CMAKE_C_FLAGS,
> making -O0 end appending to fail. To prevent this we need to avoid
> CMAKE_C_FLAGS_RELWITHDEBINFO to be appended to CMAKE_C_FLAGS, so let's
> do the same as flare-engine package that set CMAKE_BUILD_TYPE to a fake
> build type called "buildroot", this way -O2 won't be appended after -O0
> and work around restart to work as expected.
>
> Fixes:
> http://autobuild.buildroot.net/results/2e3/2e31abd7b115d4c29117ca82007fd4f87f853ff7/
>
> Signed-off-by: Giulio Benetti <giulio.benetti@benettiengineering.com>
> ---
> package/apitrace/apitrace.mk | 4 ++++
> 1 file changed, 4 insertions(+)
Applied to master, thanks. I am wondering when this bug will be fixed
in upstream gcc...
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2020-06-22 20:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-10 16:16 [Buildroot] [PATCH] package/apitrace: fix apitrace microblaze build failure Giulio Benetti
2020-06-22 20:55 ` Thomas Petazzoni [this message]
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=20200622225537.2d4764be@windsurf.home \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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