Yocto Project Discussions
 help / color / mirror / Atom feed
From: "Khem Raj" <raj.khem@gmail.com>
To: "Varangu-Booth, Valen" <Valen.Varangu-Booth@christiedigital.com>,
	yocto@lists.yoctoproject.org
Subject: Re: [yocto] Perl populate sysroot fails (yocto 2.0.3)
Date: Wed, 7 Oct 2020 15:23:36 -0700	[thread overview]
Message-ID: <72d6a6c2-68f0-bf5f-e0c4-3b3b7f5bb582@gmail.com> (raw)
In-Reply-To: <3019.1602095767259762860@lists.yoctoproject.org>



On 10/7/20 11:36 AM, Varangu-Booth, Valen wrote:
> Thanks,
> I've managed to narrow the problem down to samba - it has perl at 
> sysroot/dest-dir/usr/lib/perl5.
> However for the life of me I can't figure out how to force it to run 
> after the actual Perl recipe. I've tried adding DEPENDS += "perl" in a 
> .bbappend file (which bitbake-layers show-appends recognizes) and just 
> directly editing the recipe.
> Neither seem to make it stick. The first run right after the change 
> works (since it's able to use the cached perl, and waits to rebuild 
> samba) but subsequent runs (once samba is in the cache) always fail.
> For now I'm working around it by manually purging samba from the cache 
> after each run, but it would be nice to solve this properly at some 
> point as well.
> If anyone has any tips on where to look next to force the build order, 
> that would be great.

perhaps adding something like below to samba bbappend might help

do_populate_sysroot[depends] += "perl:do_populate_sysroot"

> 
> Thanks,
> 
> Valen
> 
> 
> 
> 

  reply	other threads:[~2020-10-07 22:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-06 20:36 Perl populate sysroot fails (yocto 2.0.3) Varangu-Booth, Valen
2020-10-06 21:01 ` [yocto] " Khem Raj
2020-10-07 18:36   ` Varangu-Booth, Valen
2020-10-07 22:23     ` Khem Raj [this message]
2020-10-08 17:27       ` Varangu-Booth, Valen

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=72d6a6c2-68f0-bf5f-e0c4-3b3b7f5bb582@gmail.com \
    --to=raj.khem@gmail.com \
    --cc=Valen.Varangu-Booth@christiedigital.com \
    --cc=yocto@lists.yoctoproject.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