All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dario Binacchi <dario.binacchi@amarulasolutions.com>
To: buildroot@buildroot.org
Cc: Dario Binacchi <dario.binacchi@amarulasolutions.com>,
	linux-amarula@amarulasolutions.com
Subject: [Buildroot] [PATCH 5/6] package/libopenssl: no-engine
Date: Fri, 21 Jun 2024 18:10:48 +0200	[thread overview]
Message-ID: <20240621161049.4085310-5-dario.binacchi@amarulasolutions.com> (raw)
In-Reply-To: <20240621161049.4085310-1-dario.binacchi@amarulasolutions.com>

Even though the "no-engine" option effectively disables the compilation
of the engine, it still creates the installation directory, which ends up
being empty. For this reason, the patch does not remove the hook for
removing the directory if the BR2_PACKAGE_LIBOPENSSL_ENGINES option is
not enabled.

Signed-off-by: Dario Binacchi <dario.binacchi@amarulasolutions.com>
---
 package/libopenssl/libopenssl.mk | 1 +
 1 file changed, 1 insertion(+)

diff --git a/package/libopenssl/libopenssl.mk b/package/libopenssl/libopenssl.mk
index fe472e2c7a19..89a9189bb851 100644
--- a/package/libopenssl/libopenssl.mk
+++ b/package/libopenssl/libopenssl.mk
@@ -85,6 +85,7 @@ define LIBOPENSSL_CONFIGURE_CMDS
 			no-fuzz-afl \
 			no-afalgeng \
 			$(if $(BR2_PACKAGE_LIBOPENSSL_BIN),,no-apps) \
+			$(if $(BR2_PACKAGE_LIBOPENSSL_ENGINES),,no-engine) \
 			$(if $(BR2_PACKAGE_LIBOPENSSL_ENABLE_CHACHA),,no-chacha) \
 			$(if $(BR2_PACKAGE_LIBOPENSSL_ENABLE_RC2),,no-rc2) \
 			$(if $(BR2_PACKAGE_LIBOPENSSL_ENABLE_RC4),,no-rc4) \
-- 
2.43.0

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  parent reply	other threads:[~2024-06-21 16:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-21 16:10 [Buildroot] [PATCH 1/6] package/libopenssl: use $(RM) instead of rm Dario Binacchi
2024-06-21 16:10 ` [Buildroot] [PATCH 2/6] package/libopenssl: replace engines-1.1 to engines-3 Dario Binacchi
2024-07-08  6:52   ` Peter Korsgaard
2024-06-21 16:10 ` [Buildroot] [PATCH 3/6] package/libopenssl: use consistent logic Dario Binacchi
2024-07-08  6:53   ` Peter Korsgaard
2024-06-21 16:10 ` [Buildroot] [PATCH 4/6] package/libopenssl: use `no-apps' configuration option Dario Binacchi
2024-07-08  6:53   ` Peter Korsgaard
2024-06-21 16:10 ` Dario Binacchi [this message]
2024-07-08  6:53   ` [Buildroot] [PATCH 5/6] package/libopenssl: no-engine Peter Korsgaard
2024-06-21 16:10 ` [Buildroot] [PATCH 6/6] package/libopenssl: add new configuration options Dario Binacchi
2024-06-23 20:59   ` Yann E. MORIN
2024-06-23 20:47 ` [Buildroot] [PATCH 1/6] package/libopenssl: use $(RM) instead of rm Yann E. MORIN
2024-07-08  6:52 ` Peter Korsgaard

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=20240621161049.4085310-5-dario.binacchi@amarulasolutions.com \
    --to=dario.binacchi@amarulasolutions.com \
    --cc=buildroot@buildroot.org \
    --cc=linux-amarula@amarulasolutions.com \
    /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.