From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <rong.fu.cn@windriver.com>, <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] perl: Fix ptest failures
Date: Tue, 26 May 2026 11:34:38 +0200 [thread overview]
Message-ID: <DISI7VNQ7EUI.1WFTMNSY1FBC4@bootlin.com> (raw)
In-Reply-To: <20260525013402.3744277-1-rong.fu.cn@windriver.com>
On Mon May 25, 2026 at 3:34 AM CEST, Rong Fu via lists.openembedded.org wrote:
> From: Jinfeng Wang <jinfeng.wang.cn@windriver.com>
Hi,
Thanks for your patch.
>
> diff --git a/meta/recipes-devtools/perl/perl-ptest.inc b/meta/recipes-devtools/perl/perl-ptest.inc
> index 4b4756118c..b33800ba54 100644
> --- a/meta/recipes-devtools/perl/perl-ptest.inc
> +++ b/meta/recipes-devtools/perl/perl-ptest.inc
> @@ -59,7 +59,8 @@ python populate_packages:prepend() {
> '${PN}-ptest%s', '%s', recursive=True, match_path=True)
> }
>
> -RDEPENDS:${PN}-ptest += "${PN}-modules ${PN}-doc sed procps-ps"
> +RDEPENDS:${PN}-ptest += "${PN}-modules ${PN}-doc sed procps-ps libxcrypt-dev"
It looks like this is failing with musl:
ERROR: Nothing RPROVIDES 'libxcrypt-dev' (but /srv/pokybuild/yocto-worker/musl-qemuarm64/build/layers/openembedded-core/meta/recipes-devtools/perl/perl_5.42.0.bb RDEPENDS on or otherwise requires it)
libxcrypt RPROVIDES libxcrypt-dev but was skipped: PREFERRED_PROVIDER_virtual/crypt set to musl, not libxcrypt
https://autobuilder.yoctoproject.org/valkyrie/#/builders/111/builds/2537
https://autobuilder.yoctoproject.org/valkyrie/#/builders/6/builds/3831
https://autobuilder.yoctoproject.org/valkyrie/#/builders/3/builds/3868
Can you have a look at the issue?
Thanks,
Mathieu
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2026-05-26 9:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-25 1:34 [PATCH] perl: Fix ptest failures rong.fu.cn
2026-05-26 9:34 ` Mathieu Dubois-Briand [this message]
2026-05-26 10:04 ` [OE-core] " Alexander Kanavin
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=DISI7VNQ7EUI.1WFTMNSY1FBC4@bootlin.com \
--to=mathieu.dubois-briand@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=rong.fu.cn@windriver.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