public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Quentin Schulz <quentin.schulz@cherry.de>
To: bruce.ashfield@gmail.com, richard.purdie@linuxfoundation.org
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 1/6] linux-yocto-dev: conditionally add coreutils to depends
Date: Mon, 14 Oct 2024 19:15:51 +0200	[thread overview]
Message-ID: <2547eb43-b75e-4d93-af32-a45324e9759e@cherry.de> (raw)
In-Reply-To: <88eada332f5d3d00baf9f2cedf63460d80356032.1728912923.git.bruce.ashfield@gmail.com>

Hi Bruce,

On 10/14/24 3:45 PM, Bruce Ashfield via lists.openembedded.org 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)}"
> +

Nice :)

Reviewed-by: Quentin Schulz <quentin.schulz@cherry.de>

For the sake of completeness, truncate is part of HOSTTOOLS in 
scarthgap-5.0.5+ (yes, not released yet) and styhead and later releases. 
We may want to backport this HOSTTOOLS+truncate patch to kirkstone as 
well maybe? So this patch here is only required for any other scenario 
:) (it's basically not useful for master branch but is nice as a hint to 
user trying to figure out how to compile 6.11 on other branches :) ).

Thanks!
Quentin


  reply	other threads:[~2024-10-14 17:16 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   ` Quentin Schulz [this message]
2024-10-15 14:15   ` Richard Purdie
2024-10-15 20:56     ` Bruce Ashfield
2024-10-15 21:01       ` Richard Purdie
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=2547eb43-b75e-4d93-af32-a45324e9759e@cherry.de \
    --to=quentin.schulz@cherry.de \
    --cc=bruce.ashfield@gmail.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