public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: [PATCH 3/7] linux-yocto/4.12: add ssl and utils native dependencies
Date: Tue, 27 Mar 2018 11:03:15 -0400	[thread overview]
Message-ID: <f431b7865fde00a8d4f9fecf85bed0c0d52f2fdb.1522162765.git.bruce.ashfield@windriver.com> (raw)
In-Reply-To: <cover.1522162765.git.bruce.ashfield@windriver.com>

Via the -stable updates, and other configuration changes the 4.12 kernel has the
same dependency on openssl headers as 4.14+.

So we add the same DEPENDS line that we already have in newer kernels to avoid the
following error:

   |   HOSTCC  scripts/sign-file
   | build/tmp/work-shared/qemux86-64/kernel-source/scripts/sign-file.c:25:30: fatal error: openssl/opensslv.h: No such file or directory
   | compilation terminated.
   | scripts/Makefile.host:107: recipe for target 'scripts/sign-file' failed
   | make[3]: *** [scripts/sign-file] Error 1
   | make[3]: *** Waiting for unfinished jobs....

Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
---
 meta/recipes-kernel/linux/linux-yocto_4.12.bb | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/meta/recipes-kernel/linux/linux-yocto_4.12.bb b/meta/recipes-kernel/linux/linux-yocto_4.12.bb
index 830634211a4d..6c82505b4796 100644
--- a/meta/recipes-kernel/linux/linux-yocto_4.12.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_4.12.bb
@@ -24,6 +24,8 @@ SRCREV_meta ?= "2feb169ba66721f3794bacd97c8360ad594ce133"
 SRC_URI = "git://git.yoctoproject.org/linux-yocto-4.12.git;name=machine;branch=${KBRANCH}; \
            git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-4.12;destsuffix=${KMETA}"
 
+DEPENDS += "openssl-native util-linux-native"
+
 LINUX_VERSION ?= "4.12.21"
 
 PV = "${LINUX_VERSION}+git${SRCPV}"
-- 
2.5.0



  parent reply	other threads:[~2018-03-27 15:03 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-27 15:03 [PATCH 0/7] linux-yocto: consolidated pull request Bruce Ashfield
2018-03-27 15:03 ` [PATCH 1/7] linux-yocto/4.12: update to v4.12.21 Bruce Ashfield
2018-03-27 15:03 ` [PATCH 2/7] mpc8315e-rdb: fix broken ethernet Bruce Ashfield
2018-03-27 15:03 ` Bruce Ashfield [this message]
2018-03-27 15:03 ` [PATCH 4/7] linux-yocto/meta: improve wifi driver granularity Bruce Ashfield
2018-03-27 15:03 ` [PATCH 5/7] linux-yocto/4.12: intel-socfpga, intel-pmc-core and ish support for CoffeeLake board Bruce Ashfield
2018-03-27 15:03 ` [PATCH 6/7] linux-yocto/4.14: update to v4.14.30 Bruce Ashfield
2018-03-27 22:07   ` Burton, Ross
2018-03-28  1:39     ` Bruce Ashfield
2018-03-27 15:03 ` [PATCH 7/7] linux-yocto/4.15: update to v4.15.13 Bruce Ashfield
2018-03-28 10:31 ` [PATCH 0/7] linux-yocto: consolidated pull request Burton, Ross
2018-03-28 10:33   ` Burton, Ross
2018-03-28 12:01     ` Bruce Ashfield
2018-03-28 12:07       ` Burton, Ross
2018-03-28 12:57         ` Bruce Ashfield
2018-03-29 12:58     ` Bruce Ashfield
2018-03-29 13:13       ` Richard Purdie
2018-03-29 13:55         ` Bruce Ashfield

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=f431b7865fde00a8d4f9fecf85bed0c0d52f2fdb.1522162765.git.bruce.ashfield@windriver.com \
    --to=bruce.ashfield@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.org \
    /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