From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] package/libnss: fix build failure on arm32 arch not armv7
Date: Sat, 4 Apr 2020 22:58:53 +0200 [thread overview]
Message-ID: <20200404225853.23c43aaa@windsurf.home> (raw)
In-Reply-To: <20200403201021.44350-1-giulio.benetti@benettiengineering.com>
On Fri, 3 Apr 2020 22:10:21 +0200
Giulio Benetti <giulio.benetti@benettiengineering.com> wrote:
> NSS assumes that every neon arm32 build is an armv7, but this is
> not always true(i.e. build arm32 for armv8), so let's add a patch to
> remove -march=armv7 flag when building gcm-arm32-neon.c
>
> Fixes:
> http://autobuild.buildroot.net/results/464/464044fda2850123339de6c8071374e380636ee0/
>
> Signed-off-by: Giulio Benetti <giulio.benetti@benettiengineering.com>
> ---
> V1->V2:
> * update with upstreamed patch:
> https://bugzilla.mozilla.org/show_bug.cgi?id=1624864
> * improve commit log
> ---
> ...t-force-ARMv7-for-gcm-arm32-neon-r-j.patch | 29 +++++++++++++++++++
> 1 file changed, 29 insertions(+)
> create mode 100644 package/libnss/0002-Bug-1624864-Don-t-force-ARMv7-for-gcm-arm32-neon-r-j.patch
Applied to master with an updated reference to the upstream patch, as
suggested by Peter Seiderer.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-04-04 20:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-03 19:45 [Buildroot] [PATCH v1] package/libnss: fix compile failure Peter Seiderer
2020-04-03 20:00 ` Giulio Benetti
2020-04-03 20:10 ` [Buildroot] [PATCH v2] package/libnss: fix build failure on arm32 arch not armv7 Giulio Benetti
2020-04-03 21:06 ` Peter Seiderer
2020-04-04 20:58 ` Thomas Petazzoni [this message]
2020-04-05 17:13 ` Giulio Benetti
2020-04-03 21:01 ` [Buildroot] [PATCH v1] package/libnss: fix compile failure Peter Seiderer
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=20200404225853.23c43aaa@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox