Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Waldemar Brodkorb <wbx@openadk.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] vlc: workaround microblaze gcc internal compiler error
Date: Mon, 27 Feb 2017 07:07:25 +0100	[thread overview]
Message-ID: <20170227060725.GA27933@waldemar-brodkorb.de> (raw)

Override gcc optimization flags with -O0.

The workaround is not required for gcc6 anymore, but
gcc6 is disabled for microblaze, because it breaks startup 
of the system somehow. So the bug is not reported upstream.

Fixes:
 http://autobuild.buildroot.net/results/a318f0838a6a602046e719103ac81965c0084d52

Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
---
 package/vlc/vlc.mk | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/package/vlc/vlc.mk b/package/vlc/vlc.mk
index 666b8d4..a523f8f 100644
--- a/package/vlc/vlc.mk
+++ b/package/vlc/vlc.mk
@@ -15,6 +15,12 @@ VLC_AUTORECONF = YES
 # Install vlc libraries in staging.
 VLC_INSTALL_STAGING = YES
 
+# gcc bug internal compiler error: in merge_overlapping_regs, at regrename.c:304
+ifeq ($(BR2_microblaze),y)
+VLC_CONF_ENV += CFLAGS="$(TARGET_CFLAGS) -O0"
+VLC_CONF_OPTS += --disable-optimizations
+endif
+
 # VLC defines two autoconf functions which are also defined by our own pkg.m4
 # from pkgconf. Unfortunately, they are defined in a different way: VLC adds
 # --enable- options, but pkg.m4 adds --with- options. To make sure we use
-- 
2.1.4

             reply	other threads:[~2017-02-27  6:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-27  6:07 Waldemar Brodkorb [this message]
2017-02-27  8:29 ` [Buildroot] [PATCH] vlc: workaround microblaze gcc internal compiler error Thomas Petazzoni
2017-02-27 20:38 ` Thomas Petazzoni

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=20170227060725.GA27933@waldemar-brodkorb.de \
    --to=wbx@openadk.org \
    --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