From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/libopenssl: fix static build on x86_64
Date: Wed, 16 Oct 2019 09:15:29 +0200 [thread overview]
Message-ID: <20191016091529.5a03c63b@windsurf> (raw)
In-Reply-To: <20191015214644.31476-1-fontaine.fabrice@gmail.com>
On Tue, 15 Oct 2019 23:46:44 +0200
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:
> Use no-asm when building statically on x86_64, see
> https://github.com/openssl/openssl/issues/9839
>
> Fixes:
> - http://autobuild.buildroot.org/results/e4f04bb13ec1b82b73db645bea4933e52bca4185
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Is the problem specific to x86-64 ? Reading the Github issue, the
OpenSSL developer apparently says that whenever the "generic"
architecture variants are used, no-asm should be passed as well. This
is not really what your patch is doing.
Could you clarify this ?
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2019-10-16 7:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-15 21:46 [Buildroot] [PATCH 1/1] package/libopenssl: fix static build on x86_64 Fabrice Fontaine
2019-10-16 7:15 ` 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=20191016091529.5a03c63b@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