Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v5, 1/1] package/libopenssl: set no-asm with generic architectures
Date: Thu, 31 Oct 2019 15:14:58 +0100	[thread overview]
Message-ID: <87imo5xaql.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20191019122759.529-1-fontaine.fabrice@gmail.com> (Fabrice Fontaine's message of "Sat, 19 Oct 2019 14:27:59 +0200")

>>>>> "Fabrice" == Fabrice Fontaine <fontaine.fabrice@gmail.com> writes:

 > Use no-asm when building with generic architectures such as gcc or
 > linux-generic32, see https://github.com/openssl/openssl/issues/9839

 > This will fix a static build failure on x86_64 due to the removal of
 > x86/x86_64 BSAES and AES_ASM support by
 > https://github.com/openssl/openssl/commit/87bea6550ae0dda7c40937cff2e86cc2b0b09491

 > Fixes:
 >  - http://autobuild.buildroot.org/results/e4f04bb13ec1b82b73db645bea4933e52bca4185

 > Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
 > ---
 > Changes v4 -> v5 (after review of Thomas Petazzoni):
 >  - Reword commit message to remove statically

 > Changes v3 -> v4 (after review of Thomas Petazzoni):
 >  - Fix copy/paste error and remove the second assignation

 > Changes v2 -> v3 (after review of Thomas Petazzoni):
 >  - Set no-asm with linux-generic32

 > Changes v1 -> v2 (after review of Thomas Petazzoni):
 >  - Set no-asm with all static builds and not only x86_64

 >  package/libopenssl/libopenssl.mk | 8 ++++++--
 >  1 file changed, 6 insertions(+), 2 deletions(-)

Committed to 2019.02.x and 2019.08.x, thanks.

-- 
Bye, Peter Korsgaard

      parent reply	other threads:[~2019-10-31 14:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-19 12:27 [Buildroot] [PATCH v5, 1/1] package/libopenssl: set no-asm with generic architectures Fabrice Fontaine
2019-10-27  9:31 ` Thomas Petazzoni
2019-10-31 14:14 ` Peter Korsgaard [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=87imo5xaql.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.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