All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Looijmans <mike.looijmans@topic.nl>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] kernel.bbclass: add lzop dependency
Date: Tue, 9 Aug 2016 14:08:13 +0200	[thread overview]
Message-ID: <57A9C7AD.9090901@topic.nl> (raw)
In-Reply-To: <20160801123253.9292-1-twoerner@gmail.com>

I've been adding "lzop-native" to a lot of kernel recipes because you also 
need it when generating an LZO compressed kernel (I like my boot time to be 
under 1 second).

It's a small dependency which is hard to automatically figure out, since there 
are a number of ways to trigger it (we just found two). I would welcome this 
patch very much, and I don't think many will suffer...


On 01-08-16 14:32, Trevor Woerner wrote:
> If the initramfs image is type lzo, then a native lzop is needed.
>
> Signed-off-by: Trevor Woerner <twoerner@gmail.com>
> ---
>   meta/classes/kernel.bbclass | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/classes/kernel.bbclass b/meta/classes/kernel.bbclass
> index fa76a14..db42744 100644
> --- a/meta/classes/kernel.bbclass
> +++ b/meta/classes/kernel.bbclass
> @@ -1,7 +1,7 @@
>   inherit linux-kernel-base kernel-module-split
>
>   PROVIDES += "virtual/kernel"
> -DEPENDS += "virtual/${TARGET_PREFIX}binutils virtual/${TARGET_PREFIX}gcc kmod-native depmodwrapper-cross bc-native"
> +DEPENDS += "virtual/${TARGET_PREFIX}binutils virtual/${TARGET_PREFIX}gcc kmod-native depmodwrapper-cross bc-native lzop-native"
>
>   S = "${STAGING_KERNEL_DIR}"
>   B = "${WORKDIR}/build"
>



  parent reply	other threads:[~2016-08-09 12:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-01 12:32 [PATCH] kernel.bbclass: add lzop dependency Trevor Woerner
2016-08-01 14:07 ` Bruce Ashfield
2016-08-01 14:08   ` Burton, Ross
2016-08-02 13:52     ` Trevor Woerner
2016-08-03 12:53     ` Trevor Woerner
2016-08-04  1:39       ` Bruce Ashfield
2016-08-05 14:24         ` Trevor Woerner
2016-08-09 12:08 ` Mike Looijmans [this message]
2016-08-09 19:27   ` Khem Raj
2016-08-10  8:59     ` Richard Purdie
2016-08-10 16:07       ` Khem Raj
2016-08-10 16:46         ` Richard Purdie

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=57A9C7AD.9090901@topic.nl \
    --to=mike.looijmans@topic.nl \
    --cc=openembedded-core@lists.openembedded.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 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.