From: Phil Reid <preid@electromag.com.au>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
openembedded-core@lists.openembedded.org
Cc: Robert Yang <liezhi.yang@windriver.com>
Subject: Re: [OE-core] [PATCH] archiver.bbclass: Fix archiver interaction with kernel recipes
Date: Fri, 11 Oct 2024 07:40:30 +0800 [thread overview]
Message-ID: <f05b8b5d-0bda-4e16-a925-9e74eeb03c8d@electromag.com.au> (raw)
In-Reply-To: <26e580e6dadced007020601689e3d7a4f2790e45.camel@linuxfoundation.org>
On 10/10/2024 15:17, Richard Purdie wrote:
> On Thu, 2024-10-10 at 13:25 +0800, Phil Reid via lists.openembedded.org
> wrote:
>> Changes to the logic of is_work_shared where made in
>> commit: 5fbb4ca8da4f4f1ea426275c45634802dcb5a575
>> "archiver.bbclass: Improve work-shared checking"
>>
>> The resuled in a change of the logic (simplifed here) from:
>> inherits(gcc-source) or inherits(kernel) or (inherits(kernelsrc)
>> and srcin(work-shared))
>> to just
>> srcin(work-shared)
>>
>> With INHERIT += "archiver" in the local.conf and a kernel recipe that
>> uses
>> KERNEL_PACKAGE_NAME. When KERNEL_PACKAGE_NAME is defined the kernel
>> source is not placed into work-shared, but the archiver ends up
>> deleting the source folder in the work dir, and the build
>> subsequently fails.
>>
>> Restore the previous logic while also mainting the referenced commits
>> intent
>> to consider all recipes that use work-shared. Logic is now
>> inherits(gcc-source) or inherits(kernel) or srcin(work-shared)
>>
>> Signed-off-by: Phil Reid <preid@electromag.com.au>
>> ---
>> meta/classes/archiver.bbclass | 5 ++++-
>> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> You're effectively reverting that commit whilst changing the logic so
> it looks slightly different.
>
> Was there a problem with gcc-source archiving as I notice the patch
> adds gcc-source back too?
To be honest I didn't test without the gcc-source, I reverted the commit first after
finding that commit to be the cause and modified it so it consider it always considered
work-shared path and called it done and the old logic conditions.
>
> The commit message isn't quite accurate as gcc-source isn't something
> which gets inherited.
Fair enough.
>
> Does this only happen with kernel recipes which use
> KERNEL_PACKAGE_NAME? That might be the key missing detail which would
> allow us to reproduce the failure.
>
I haven't seen the problem on a virtual/kernel.
When KERNEL_PACKAGE_NAME is specified the kernel source isn't put into work-shared.
How would you like to see this fixed?
--
Regards
Phil Reid
ElectroMagnetic Imaging Technology Pty Ltd
Development of Geophysical Instrumentation & Software
www.electromag.com.au
23 Junction Parade, Midland WA 6056, AUSTRALIA
Ph: +61 8 9250 8100
Fax: +61 8 9250 7100
Email: preid@electromag.com.au
next prev parent reply other threads:[~2024-10-10 23:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-10 5:25 [OE-core] [PATCH] archiver.bbclass: Fix archiver interaction with kernel recipes Phil Reid
2024-10-10 7:17 ` Richard Purdie
2024-10-10 23:40 ` Phil Reid [this message]
2024-10-11 11:57 ` Richard Purdie
2024-11-01 12:02 ` Robert Yang
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=f05b8b5d-0bda-4e16-a925-9e74eeb03c8d@electromag.com.au \
--to=preid@electromag.com.au \
--cc=liezhi.yang@windriver.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