From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: Marco Felsch <m.felsch@pengutronix.de>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] Revert "kernel.bbclass: make dependency on lzop-native conditional"
Date: Tue, 06 Oct 2020 15:27:37 +0100 [thread overview]
Message-ID: <d988f9d69fdbc8fde674b0e2041d92a6807e26a9.camel@linuxfoundation.org> (raw)
In-Reply-To: <20201006142607.axiegefkixioktnf@pengutronix.de>
On Tue, 2020-10-06 at 16:26 +0200, Marco Felsch wrote:
> On 20-10-06 14:27, Richard Purdie wrote:
> > On Mon, 2020-10-05 at 16:18 +0200, Marco Felsch wrote:
> > > This reverts commit 1217ddf070261c5fe523729b2a833bd38f1e4ccd.
> > >
> > > This commit breaks compiling if no initramfs is used because the
> > > kernel image can be compressed too using lzo.
> >
> > Can we detect if the kernel is due to be compressed with lzo
> > through
> > any of our configuration variables?
>
> I thought about it too.. We need to grep the .config and check if the
> Kconfig was set either by the defconfig we are providing or by some
> inheritance.
Grepping the .config isn't an option as we need to determine this at
parse time. I did wondering the kernel type/output name style variables
would tell us but it sounds like that isn't the case :(
Cheers,
Richard
next prev parent reply other threads:[~2020-10-06 14:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-05 14:18 [PATCH] Revert "kernel.bbclass: make dependency on lzop-native conditional" Marco Felsch
2020-10-06 13:27 ` [OE-core] " Richard Purdie
2020-10-06 14:26 ` Marco Felsch
2020-10-06 14:27 ` Richard Purdie [this message]
2020-10-06 15:57 ` Marco Felsch
2020-10-07 11:28 ` Richard Purdie
2020-10-07 15:59 ` Marco Felsch
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=d988f9d69fdbc8fde674b0e2041d92a6807e26a9.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=m.felsch@pengutronix.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox