All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC v1] WIP: package/qt5webengine: fix compile flags for rpi zero
Date: Sun, 23 Feb 2020 22:12:25 +0100	[thread overview]
Message-ID: <20200223221225.212c8f4a@windsurf> (raw)
In-Reply-To: <20200220224938.13945-1-ps.report@gmx.net>

Hello Peter,

On Thu, 20 Feb 2020 23:49:38 +0100
Peter Seiderer <ps.report@gmx.net> wrote:

> The qt5webengine configure simple takes QT_ARCH ('arm') to determine the
> chromium compiler flags resulting in wrong defaults for the rpi
> zero case (resulting in illegal instruction failure), e.g.:
> 	-march=armv7-a -mfloat-abi=hard -mtune=generic-armv7-a -mfpu=vfpv3-d16
> 
> Add patch to overwrite the chromium settings with suitable values
> for the rpi zero case in the file rc/3rdparty/chromium/build/config/arm.gni.
> 
> Fixes:
> 
>   $ /usr/lib/qt/examples/webengine/minimal/minimal
>   Illegal instruction
> 
> Signed-off-by: Peter Seiderer <ps.report@gmx.net>
> ---
> Notes:
>   - Work-In-Progress patch to test the prinziple of chromium configuration
>     for the rpi zero case, do not apply. A real fix should set the
>     values in arm.gni determined from the buildroot configuration.

I was indeed going to ask: why do we care about the RPi Zero
specifically?

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

      reply	other threads:[~2020-02-23 21:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-20 22:49 [Buildroot] [RFC v1] WIP: package/qt5webengine: fix compile flags for rpi zero Peter Seiderer
2020-02-23 21:12 ` 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=20200223221225.212c8f4a@windsurf \
    --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.