All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot raspberrypi3_qt5we_defconfig no longer builds
Date: Tue, 20 Aug 2019 14:17:08 +0200	[thread overview]
Message-ID: <20190820141708.54fbccac@windsurf.home> (raw)
In-Reply-To: <20190820114359.cw5qcdpku37q26ic@archlinux.localdomain>

Hello Ga?l,

On Tue, 20 Aug 2019 07:43:59 -0400
Ga?l PORTAY <gael.portay@collabora.com> wrote:

> I had a look that week end.
> 
> I observed that there is some -isystem CFLAGS in the generated ninja
> files.
> 
> 	-isystem../../../../../host/arm-buildroot-linux-gnueabihf/sysroot/usr/include/libpng16
> 	-isystem../../../../../host/arm-buildroot-linux-gnueabihf/sysroot/usr/include
> 	-isystem../../../../../host/arm-buildroot-linux-gnueabihf/sysroot/usr/include/freetype2
> 
> If I substitute the -isystem in -I, the file compile then but webgengine
> fails to the next subproject with -isystem flags.
> 
> IIUC, qtwebengine uses qmake that uses ng to generate ninja files.
> 
> I am looking for the culprit that introduces the -isystem flags. I am
> not yet familiar with ng/ninja, and I have basic knowledge of
> qmake only.

Did you check https://bugreports.qt.io/browse/QTBUG-53367, which seems
related, but more for qmake-generated Makefiles.

We have https://bugs.busybox.net/show_bug.cgi?id=11776, which is in
fact reporting two different qt5webengine issues, the second being the
same as the one you are facing.

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

      reply	other threads:[~2019-08-20 12:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-10  8:30 [Buildroot] Buildroot raspberrypi3_qt5we_defconfig no longer builds Thomas Petazzoni
2019-08-13 12:48 ` Gaël PORTAY
2019-08-18 12:43   ` Thomas Petazzoni
2019-08-20 11:43     ` Gaël PORTAY
2019-08-20 12:17       ` 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=20190820141708.54fbccac@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.