All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/qt5/qt5webengine: fix build error
Date: Sun, 11 Aug 2019 22:30:51 +0200	[thread overview]
Message-ID: <20190811223051.707ac1a8@windsurf.home> (raw)
In-Reply-To: <ff0a929f-f321-7eb6-a9ea-91abd85bacf5@grinn-global.com>

Hello,

On Wed, 31 Jul 2019 09:15:13 +0200
Bartosz Bi?as <b.bilas@grinn-global.com> wrote:

> --sysroot=../../../../../host/arm-buildroot-linux-gnueabihf/sysroot 
> -fvisibility-inlines-hidden -c 
> ../../3rdparty/chromium/third_party/skia/third_party/skcms/skcms.cc -o 
> obj/skia/skcms/skcms.o
> ../../3rdparty/chromium/third_party/skia/third_party/skcms/src/Transform_inl.h: 
> In function ?void exec_ops(const Op*, const void**, const char*, char*, 
> int)?:
> ../../3rdparty/chromium/third_party/skia/third_party/skcms/src/Transform_inl.h:560:16: 
> internal compiler error: in convert_move, at expr.c:231
>  ?static void NS(exec_ops)(const Op* ops, const void** args,
>  ??????????????? ^
> ../../3rdparty/chromium/third_party/skia/third_party/skcms/skcms.cc:1909:16: 
> note: in definition of macro ?NS?
>  ?#define NS(id) id
>  ??????????????? ^~
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See <http://bugs.buildroot.net/> for instructions.
> [1902/14080] CXX obj/skia/skia_core_and_effects/SkMipMap.o
> ninja: build stopped: subcommand failed.

Then I'm still confused.

What is the relationship between the patch you're posting and the build
error ? It seems entirely unrelated at first sight.

Is it the requirement of gcc >= 8.x that works around the compiler
bug ? Is there a gcc bug report for this compiler bug ?

Some googling leads to
https://github.com/OSSystems/meta-browser/issues/135, which itself
links to https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83623.

It seems like the bug has been fixed in both the gcc 6.x (fix was in gcc 6.5.0) and gcc 7.x
branches (fix was in gcc 7.3.0).

So, could you give more details about the situation in which you're
encountering this build failure ? Which toolchain are you using ? How
is the patch related to the build failure ?

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2019-08-11 20:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-30 11:58 [Buildroot] [PATCH] package/qt5/qt5webengine: fix build error Bartosz Bilas
2019-07-30 14:03 ` Thomas Petazzoni
2019-07-30 16:06   ` Bartosz Biłas
2019-07-30 21:30 ` Peter Seiderer
2019-07-31  7:15   ` Bartosz Biłas
2019-08-11 20:30     ` Thomas Petazzoni [this message]
2019-09-04 11:54       ` Andreas Naumann
2019-12-20 11:43       ` Giulio Benetti
2019-12-20 17:16         ` Bartosz Bilas
2020-04-01 15:03         ` Thomas Petazzoni
2020-04-02  5:35           ` 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=20190811223051.707ac1a8@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.