From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: Jacob Kroon <jacob.kroon@gmail.com>,
"T. Ulrich" <timon.ulrich@kabelmail.de>,
openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH v2] kernel.bbclass: add lz4 dependency and fix the call to lz4
Date: Fri, 03 Jul 2020 14:31:09 +0100 [thread overview]
Message-ID: <5495a287c87c02af4ac4114c8fe69e63a7f9bc6b.camel@linuxfoundation.org> (raw)
In-Reply-To: <d457e91e-8345-b9ea-49c0-e4654b64398a@gmail.com>
On Fri, 2020-07-03 at 15:10 +0200, Jacob Kroon wrote:
> On 7/3/20 2:46 PM, Jacob Kroon wrote:
> > On 7/3/20 2:39 PM, T. Ulrich wrote:
> > > From: Timon Ulrich <t.ulrich@anapur.de>
> > >
> > > If the initramfs image is type lz4, then a native lz4 is needed.
> > >
> > > Additionally an output filename needs to be specified when calling lz4,
> > > otherwise STDOUT will be used implicitly.
> > >
> > > Signed-off-by: Timon Ulrich <t.ulrich@anapur.de>
> > > ---
> > > meta/classes/kernel.bbclass | 3 ++-
> > > 1 file changed, 2 insertions(+), 1 deletion(-)
> > >
> > > diff --git a/meta/classes/kernel.bbclass b/meta/classes/kernel.bbclass
> > > index 6d07b29e2d..9e3c34ad48 100644
> > > --- a/meta/classes/kernel.bbclass
> > > +++ b/meta/classes/kernel.bbclass
> > > @@ -5,6 +5,7 @@ KERNEL_DEPLOYSUBDIR ??= "${@ "" if
> > > (d.getVar("KERNEL_PACKAGE_NAME") == "kernel")
> > > PROVIDES += "${@ "virtual/kernel" if
> > > (d.getVar("KERNEL_PACKAGE_NAME") == "kernel") else "" }"
> > > DEPENDS += "virtual/${TARGET_PREFIX}binutils
> > > virtual/${TARGET_PREFIX}gcc kmod-native bc-native lzop-native
> > > bison-native"
> > > +DEPENDS += "${@bb.utils.contains("INITRAMFS_FSTYPES", "cpio.lz4",
> > > "lz4-native", "", d)}"
> >
> > Should/Could we do a similar thing for "lzop-native" above ? To me it
> > looks like that would be possible, assuming I interpreted my taskexp
> > correctly.
> >
>
> I took the liberty of doing some more history digging, lzop-native
> dependency was added in OE-Core commit
>
> ee0640cb0c32b959ffaaac6752d582ed1d76e313
> kernel.bbclass: add lzop dependency
>
> and it looks to me it'd be worth doing the same fix.
Agreed, I was hoping that would be possible for this too.
Cheers,
Richard
next prev parent reply other threads:[~2020-07-03 13:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <140262>
2020-07-03 12:39 ` [PATCH v2] kernel.bbclass: add lz4 dependency and fix the call to lz4 T. Ulrich
2020-07-03 12:46 ` [OE-core] " Jacob Kroon
2020-07-03 13:10 ` Jacob Kroon
2020-07-03 13:31 ` Richard Purdie [this message]
2020-07-03 13:50 ` [OE-core] [PATCH v2] kernel.bbclass: add lz4 dependency and fixthe " T. Ulrich
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=5495a287c87c02af4ac4114c8fe69e63a7f9bc6b.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=jacob.kroon@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=timon.ulrich@kabelmail.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