From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] kernel: need openssl since v4.3
Date: Fri, 31 Mar 2017 16:49:25 +0200 [thread overview]
Message-ID: <20170331144925.dxwrw7ywu4ahlwxn@pengutronix.de> (raw)
In-Reply-To: <1490970648-5749-1-git-send-email-niebelm@tqsc.de>
On Fri, Mar 31, 2017 at 04:30:48PM +0200, Markus Niebel wrote:
> 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
I think the documentation is a bit misleading. Since v4.3 it needs openssl
development packages _if_ module signing is enabled. Or have you seen
anything else that needs openssl?
If not, then this should be an option like KERNEL_LZOP.
Michael
> Signed-off-by: Markus Niebel <Markus.Niebel@tq-group.com>
> ---
> platforms/kernel.in | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/platforms/kernel.in b/platforms/kernel.in
> index 8b16739..69b326f 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
> prompt "Linux kernel "
>
> if KERNEL
> --
> 1.9.1
>
>
> _______________________________________________
> ptxdist mailing list
> ptxdist@pengutronix.de
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2017-03-31 14:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-31 14:30 Markus Niebel
2017-03-31 14:49 ` Michael Olbrich [this message]
2017-03-31 15:15 ` Markus Niebel
2017-03-31 15:22 ` 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=20170331144925.dxwrw7ywu4ahlwxn@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--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