Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/libnss: fix build failure due to HW PPC Crypto bug
Date: Wed, 1 Jan 2020 16:32:58 +0100	[thread overview]
Message-ID: <20200101163258.13c7de62@windsurf> (raw)
In-Reply-To: <a1f74ad6-8dbc-e515-1393-c81ec6013472@benettiengineering.com>

On Wed, 1 Jan 2020 00:44:09 +0100
Giulio Benetti <giulio.benetti@benettiengineering.com> wrote:

> >> So if we stick with nss-3.48, the package should likely depend on
> >> BR2_TOOLCHAIN_GCC_AT_LEAST_8.  
> 
> This ^^^ is too restrictive, but...
> 
> > Or don't utilize PPC hardware accelerated instructions by undefining
> > USE_PPC_CRYPTO... which is probably the saner option :-). This would
> > give the semblance that the compile worked as expected since the hashing
> > function will now be available, but Thomas' concern re CPU_ARCH and the
> > future inclusion of ppc specific source is still valid.  
> 
> ...this is a good idea. So with gcc version < 8.x let's disable 
> USE_PPC_CRYPTO and with gcc version >= 8.x let's enable it only if 
> LITTLE_ENDIAN. So at this point I would change my upstream patch to do 
> that in NSS, since there's already a gcc version check but only against 
> version 5.x(>=) that instead needs to be >= 8.x.

As I said in my previous e-mail, I also don't see how it can work with
the current OS_TEST value that we pass in libnss.mk, which is never set
to ppc64 or ppc64le as the libnss build system expects.

Best regards,

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

  parent reply	other threads:[~2020-01-01 15:32 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-27 16:54 [Buildroot] [PATCH] package/libnss: fix build failure due to HW PPC Crypto bug Giulio Benetti
2019-12-27 17:05 ` Giulio Benetti
2019-12-31 17:07 ` Thomas Petazzoni
2019-12-31 21:24   ` Giulio Benetti
2019-12-31 22:49     ` Vincent Fazio
2019-12-31 23:31       ` Vincent Fazio
2019-12-31 23:44         ` Giulio Benetti
2020-01-01  8:47           ` Yann E. MORIN
2020-01-01 15:32           ` Thomas Petazzoni [this message]
2020-01-01 16:51             ` Giulio Benetti
2020-01-01 16:58             ` [Buildroot] [PATCH v2] " Giulio Benetti
2020-01-01 18:41               ` Yann E. MORIN
2020-01-02  9:06               ` Thomas Petazzoni
2020-01-02 17:19                 ` Giulio Benetti
2020-01-02 22:07                   ` Giulio Benetti

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=20200101163258.13c7de62@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox