All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 13751] libopenssl (static): huge drop in performance in newer versions of buildroot
Date: Mon, 12 Apr 2021 20:07:52 +0000	[thread overview]
Message-ID: <bug-13751-163-Y2XLIhYcNf@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-13751-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=13751

--- Comment #1 from Arnout Vandecappelle <arnout@mind.be> ---
(In reply to maksis33 from comment #0)
> I'd assume that the issue has something to do with
> http://lists.busybox.net/pipermail/buildroot/2019-October/263030.html
> as the OpenSSL target arch is "gcc no-asm" in Buildroot 2021.02.1 while 2019.02
> targets "linux-x86_64" and also has various *_ASM flags present in the Makefile.

The culprit is actually the following commit:

commit 8c2c959b028d44f5518d4445f864aedae3d90406
Author: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Date:   Fri May 31 15:39:28 2019

    package/libopenssl: fix static build

    no-dso option has been removed with
   
https://github.com/openssl/openssl/commit/31b6ed76dfd53529b74e79830c81372d0b756929

    To fix this error, use "gcc" target in static builds. This target is
    very minimalistic, we need to manually pass -lpthread and
    -DOPENSSL_THREADS however we can also remove libdl workarounds

    Fixes:
     -
http://autobuild.buildroot.org/results/96d6b89d20980e8f7fa450b832474a81d492b315

    Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
    Signed-off-by: Peter Korsgaard <peter@korsgaard.com>


The problem is that in a static build, you don't have shared libraries so also
no DSO (the shared library provided by the kernel).


The upstream commit also adds a preprocessor symbol DSO_NONE (which is not set
by anything). So you could try reverting buildroot commit
8c2c959b028d44f5518d4445f864aedae3d90406 and add -DDSO_NONE to
LIBOPENSSL_CFLAGS.

Of course the revert is not entirely trivial, because the code was refactored
and has moved to Config.in...

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  reply	other threads:[~2021-04-12 20:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-12  9:23 [Buildroot] [Bug 13751] New: libopenssl (static): huge drop in performance in newer versions of buildroot bugzilla at busybox.net
2021-04-12 20:07 ` bugzilla at busybox.net [this message]
2021-05-04  5:50 ` [Buildroot] [Bug 13751] " bugzilla at busybox.net
2021-05-04  8:54 ` bugzilla at busybox.net
2021-05-04 19:26 ` bugzilla at busybox.net
2021-05-07  8:40 ` bugzilla at busybox.net

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=bug-13751-163-Y2XLIhYcNf@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --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.