mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Markus Niebel <niebelm@tqsc.de>
To: ptxdist@pengutronix.de
Cc: Markus Niebel <Markus.Niebel@tq-group.com>
Subject: [ptxdist] [PATCH v2] kernel: need openssl since v4.3
Date: Fri, 31 Mar 2017 17:45:38 +0200	[thread overview]
Message-ID: <1490975138-1778-1-git-send-email-niebelm@tqsc.de> (raw)

From: Markus Niebel <Markus.Niebel@tq-group.com>

regarding to https://www.kernel.org/doc/Documentation/Changes
kernel needs openssl to compile since v4.3

This is true only for use cases like module signing and trusted keyring
for things like IMA. Add hostside openssl as an optional dependency

Signed-off-by: Markus Niebel <Markus.Niebel@tq-group.com>
---
Changes since v1

make dependency optional as suggested by M. Olbrich

 platforms/kernel.in | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/platforms/kernel.in b/platforms/kernel.in
index 8b16739..4893353 100644
--- a/platforms/kernel.in
+++ b/platforms/kernel.in
@@ -9,6 +9,7 @@ menuconfig KERNEL
 	select HOST_LZOP		if KERNEL_LZOP
 	select HOST_LIBKMOD		if KERNEL_MODULES
 	select HOST_SYSTEM_BC
+	select HOST_OPENSSL		if KERNEL_OPENSSL
 	prompt "Linux kernel                  "
 
 if KERNEL
@@ -236,6 +237,15 @@ config KERNEL_LZOP
 	  Select this if you're unsure, as it won't hurt. It just
 	  increases the build time.
 
+config KERNEL_OPENSSL
+	prompt "build openssl hosttool"
+	bool
+	help
+	  Select this if you're going to build your kernel with support for
+	  module signing, IMA etc. where openssl is need as hosttool
+
+	  Select this if you're unsure, as it won't hurt. It just
+	  increases the build time.
 
 menu "patching & configuration      "
 
-- 
1.9.1


_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

             reply	other threads:[~2017-03-31 15:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-31 15:45 Markus Niebel [this message]
2017-04-03  8:31 ` Michael Olbrich

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=1490975138-1778-1-git-send-email-niebelm@tqsc.de \
    --to=niebelm@tqsc.de \
    --cc=Markus.Niebel@tq-group.com \
    --cc=ptxdist@pengutronix.de \
    /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