From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Bruce Ashfield <bruce.ashfield@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/6] linux-yocto-dev: conditionally add coreutils to depends
Date: Tue, 15 Oct 2024 22:01:38 +0100 [thread overview]
Message-ID: <884bed91ca885d594970e2141a56576363436143.camel@linuxfoundation.org> (raw)
In-Reply-To: <CADkTA4MGh=XDy+gCx7wYd-AvLCGweMFLTR_4hHQZ+tT36xUsDg@mail.gmail.com>
On Tue, 2024-10-15 at 16:56 -0400, Bruce Ashfield wrote:
> On Tue, Oct 15, 2024 at 10:15 AM Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> >
> > On Mon, 2024-10-14 at 09:45 -0400, bruce.ashfield@gmail.com wrote:
> > > From: Bruce Ashfield <bruce.ashfield@gmail.com>
> > >
> > > 6.11+ uses truncate as part of the build. While truncate has been
> > > added to HOSTTOOLS in oe-core master, it still is possible to
> > > build a kernel recipe newer than 6.11+ on a release that doesn't
> > > have the HOSTTOOLS tweak.
> > >
> > > We can test for truncate and condtionally add the dependency.
> > >
> > > Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
> > > ---
> > > meta/recipes-kernel/linux/linux-yocto-dev.bb | 4 ++++
> > > 1 file changed, 4 insertions(+)
> > >
> > > diff --git a/meta/recipes-kernel/linux/linux-yocto-dev.bb b/meta/recipes-kernel/linux/linux-yocto-dev.bb
> > > index 292897ce43..752d108bd8 100644
> > > --- a/meta/recipes-kernel/linux/linux-yocto-dev.bb
> > > +++ b/meta/recipes-kernel/linux/linux-yocto-dev.bb
> > > @@ -44,6 +44,10 @@ PACKAGECONFIG[dt-validation] = ",,python3-dtschema-native"
> > > # we need the wrappers if validation isn't in the packageconfig
> > > DEPENDS += "${@bb.utils.contains('PACKAGECONFIG', 'dt-validation', '', 'python3-dtschema-wrapper-native', d)}"
> > >
> > > +# 6.11+ uses truncate in the build, so we need to either have it in host tools, or
> > > +# build it ourselves
> > > +DEPENDS += "${@bb.utils.contains('HOSTTOOLS', 'truncate', '', 'coreutils-native', d)}"
> > > +
> > > COMPATIBLE_MACHINE = "^(qemuarmv5|qemuarm|qemuarm64|qemux86|qemuppc|qemumips|qemumips64|qemux86-64|qemuriscv32|qemuriscv64|qemuloongarch64)$"
> > >
> > > KERNEL_DEVICETREE:qemuarmv5 = "arm/versatile-pb.dtb"
> >
> > This is for master so truncate should always be in HOSTTOOLS? I don't
> > understand why we need this there?
>
> It came out of a discussion to do a reference for people that are building
> newer kernels on older releases (of which there seem to be quite a few).
>
> So either we'd have to bacckport the hosttools addition (which is likely
> possible), or I could throw together that reference of how you'd build it
> conditionally.
I think the addition was backported for scarthgap so we're good there.
The main question would be around kirkstone where this commit could be
more appropriate if someone were building 6.11+.
I'm find with having this patch around as a proof of concept but I
don't think it should go into master...
Cheers,
Richard
next prev parent reply other threads:[~2024-10-15 21:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-14 13:45 [PATCH 0/6] linux-yocto: consolidated pull request bruce.ashfield
2024-10-14 13:45 ` [PATCH 1/6] linux-yocto-dev: conditionally add coreutils to depends bruce.ashfield
2024-10-14 17:15 ` [OE-core] " Quentin Schulz
2024-10-15 14:15 ` Richard Purdie
2024-10-15 20:56 ` Bruce Ashfield
2024-10-15 21:01 ` Richard Purdie [this message]
2024-10-15 21:09 ` Bruce Ashfield
2024-10-14 13:45 ` [PATCH 2/6] linux-yocto/6.10: update to v6.10.12 bruce.ashfield
2024-10-14 13:45 ` [PATCH 3/6] linux-yocto/6.10: update to v6.10.13 bruce.ashfield
2024-10-14 13:45 ` [PATCH 4/6] linux-yocto-dev: bump to v6.12 bruce.ashfield
2024-10-14 13:45 ` [PATCH 5/6] linux-yocto/6.6: update to v6.6.54 bruce.ashfield
2024-10-14 13:45 ` [PATCH 6/6] linux-yocto/6.10: update to v6.10.14 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=884bed91ca885d594970e2141a56576363436143.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=bruce.ashfield@gmail.com \
--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