From: Markus Niebel <niebelm@tqsc.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] kernel: need openssl since v4.3
Date: Fri, 31 Mar 2017 17:15:29 +0200 [thread overview]
Message-ID: <1490973329.30305.5.camel@niebel-ws> (raw)
In-Reply-To: <20170331144925.dxwrw7ywu4ahlwxn@pengutronix.de>
Hi
Am Freitag, den 31.03.2017, 16:49 +0200 schrieb Michael Olbrich:
> 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.
>
log just from our buildserver (linux 4.6):
HOSTCC scripts/extract-cert
scripts/sign-file.c:25:30: fatal error: openssl/opensslv.h: No such file or directory
#include <openssl/opensslv.h>
^
compilation terminated.
scripts/extract-cert.c:21:25: fatal error: openssl/bio.h: No such file or directory
#include <openssl/bio.h>
^
compilation terminated.
make[2]: *** [scripts/sign-file] Error 1
The compilation is triggered by
hostprogs-$(CONFIG_SYSTEM_TRUSTED_KEYRING) += extract-cert
So I think this is (potentially) wider use case. I'm not the expert for
this kind of stuff. Can send v2 with same approach as KERNEL_LZOP
Markus
> 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
>
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2017-03-31 15:15 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
2017-03-31 15:15 ` Markus Niebel [this message]
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=1490973329.30305.5.camel@niebel-ws \
--to=niebelm@tqsc.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