From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Peter Suti <peter.suti@streamunlimited.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] externalsrc: fix dependency chain issues
Date: Mon, 07 Aug 2023 13:55:15 +0100 [thread overview]
Message-ID: <0577cb4c48dfa9610eb087ba4cf1694639dc59d7.camel@linuxfoundation.org> (raw)
In-Reply-To: <CACMGZgbW4aKKTQP1bw2YWyJBQX=KdxC2S1Z9yFaS_Q1n0CKL+A@mail.gmail.com>
On Mon, 2023-08-07 at 13:19 +0200, Peter Suti wrote:
> On Fri, Aug 4, 2023 at 4:47 PM Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> >
> > Do you have a way to reproduce this using recipes in OE-Core?
> >
> > For example, I tried adding this to the cairo recipe:
> >
> > EXTERNALSRC = "/xxx/cairo-1.16.0"
> > inherit externalsrc
> >
> > and then building cairo, cleaning cairo, building pango (which depends
> > on cairo). I couldn't see any failure.
> >
>
> To reproduce you need a transitive dependency on a recipe using
> externalsrc and run populate_sysroot.
>
> I can trigger it with the following sequence:
> 1) make cairo inherit externalsrc just like you described above.
> 2) build a package that depends on pango, for example libfm: bitbake libfm
> 3) clean cairo sstate: bitbake -c cleansstate cairo
> 4) rerun prepare_recipe_sysroot for libfm: bitbake -c
> prepare_recipe_sysroot -f libfm
>
> This produces the following error for me:
> ERROR: libfm-1.3.2-r0 do_prepare_recipe_sysroot: The sstate manifest
> for task 'cairo:populate_sysroot' (multilib variant '') could not be
> found.
> The pkgarchs considered were: armv8a-crc, armv8a, aarch64, allarch,
> x86_64_x86_64-nativesdk.
> But none of these manifests exists:
> /home/yocto/.build-yocto/tmp/sstate-control/manifest-armv8a-crc-cairo.populate_sysroot
> /home/yocto/.build-yocto/tmp/sstate-control/manifest-armv8a-cairo.populate_sysroot
> /home/yocto/.build-yocto/tmp/sstate-control/manifest-aarch64-cairo.populate_sysroot
> /home/yocto/.build-yocto/tmp/sstate-control/manifest-allarch-cairo.populate_sysroot
> /home/yocto/.build-yocto/tmp/sstate-control/manifest-x86_64_x86_64-nativesdk-cairo.populate_sysroot
> ERROR: Logfile of failure stored in:
> /home/yocto/.build-yocto/tmp/work/armv8a-poky-linux/libfm/1.3.2-r0/temp/log.do_prepare_recipe_sysroot.3102616
> ERROR: Task (/home/yocto/poky/meta/recipes-support/libfm/libfm_1.3.2.bb:do_prepare_recipe_sysroot)
> failed with exit code '1'
>
> > > I'd like to thank you for the time you have invested in this issue! I
> > > appreciate the help.
> > > I understand that my proposed solution might not be ideal, but fixing
> > > the underlying issue in runqueue would be a real challenge.
> > > If upstream is not interested in this patch, I can also understand that.
> >
> > It isn't that we're not interested, we just need to make sure something
> > else doesn't break. A test case to reproduce the issue you're seeing
> > would help a lot. Ultimately we should perhaps add something to the
> > tests in meta/lib/oeqa/ to cover the issue.
>
> I agree that a test would be valuable for this. I'll try to look into
> how such a testcase could be constructed.
I tried:
bitbake libfm; bitbake -c cleansstate cairo; bitbake -c prepare_recipe_sysroot -f libfm
with cairo marked as externalsrc and everything built just fine. Can
you confirm which release of the project you're using please? I tested
with master.
Cheers,
Richard
next prev parent reply other threads:[~2023-08-07 12:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-31 9:34 [PATCH] externalsrc: fix dependency chain issues Peter Suti
2023-07-31 10:15 ` [OE-core] " Richard Purdie
2023-07-31 10:43 ` Peter Suti
2023-07-31 11:06 ` Richard Purdie
2023-07-31 12:08 ` Peter Suti
2023-07-31 12:33 ` Richard Purdie
2023-08-02 9:26 ` Peter Suti
2023-08-04 14:47 ` Richard Purdie
2023-08-07 11:19 ` Peter Suti
2023-08-07 12:55 ` Richard Purdie [this message]
2023-08-07 14:15 ` Peter Suti
2023-08-08 7:21 ` Richard Purdie
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=0577cb4c48dfa9610eb087ba4cf1694639dc59d7.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=peter.suti@streamunlimited.com \
/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