All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 12131] qt5webengine builderror in the latest stable Buildroot 2019.05.01 version
Date: Mon, 26 Aug 2019 20:48:58 +0000	[thread overview]
Message-ID: <bug-12131-163-jiu2S5I5Je@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-12131-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=12131

--- Comment #4 from Giulio Benetti <giulio.benetti@micronovasrl.com> ---
Hello Patrick,

this bug has already been fixed here with this commit:
https://git.busybox.net/buildroot/commit/?id=3a0ed5d25e26cb2ec99a1da077c9dcfea67b0ecc

What makes it show again is that you specify '-device imx6' in
BR2_PACKAGE_QT5BASE_CUSTOM_CONF_OPTS.

When buildroot builds qt5 expects to use device 'buildroot' that is based on
qmake.conf.in in 'package/qt5/qt5base/'

So basically you're telling to qt5 to ignore buildroot qt5 configuration.

You should only remove '-device imx6' from your
BR2_PACKAGE_QT5BASE_CUSTOM_CONF_OPTS.

What is passed to qt5 build system when '-device imx6' is specified should be
implicit when you choose the correct compiler. I mean these:
IMX6_CFLAGS             = -march=armv7-a -mfpu=neon -DLINUX=1 -DEGL_API_FB=1

So if you compile for armv7-a with neon enable you should be ok.

Anyway I've tried this using master branch and I get a GCC ICE :/ and need to
dig deeper.

But please, give a try with 2019.05.1 and let me know.

Thank you!

Giulio

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2019-08-26 20:48 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-22 12:29 [Buildroot] [Bug 12131] New: qt5webengine builderror in the latest stable Buildroot 2019.05.01 version bugzilla at busybox.net
2019-08-22 12:45 ` [Buildroot] [Bug 12131] " bugzilla at busybox.net
2019-08-22 12:46 ` bugzilla at busybox.net
2019-08-22 12:47 ` bugzilla at busybox.net
2019-08-22 12:49 ` bugzilla at busybox.net
2019-08-26 20:48 ` bugzilla at busybox.net [this message]
2019-08-26 20:52 ` bugzilla at busybox.net
2019-08-29 11:27 ` bugzilla at busybox.net
2019-08-29 11:34 ` bugzilla at busybox.net
2019-08-29 11:57 ` bugzilla at busybox.net
2019-08-29 11:59 ` bugzilla at busybox.net
2019-08-29 14:55 ` bugzilla at busybox.net
2019-08-29 14:55 ` bugzilla at busybox.net
2019-08-29 15:07 ` bugzilla at busybox.net
2019-08-29 18:49 ` bugzilla at busybox.net
2019-10-05 18:11 ` bugzilla at busybox.net
2019-10-05 18:15 ` bugzilla at busybox.net
2020-12-17  4:59 ` bugzilla at busybox.net
2022-09-18 10:51 ` bugzilla

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=bug-12131-163-jiu2S5I5Je@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --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.