From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: "Pratik Farkase" <pratik.farkase@est.tech>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Cc: "pratik.farkase@ericsson.com" <pratik.farkase@ericsson.com>
Subject: Re: [OE-core][PATCH v3] libffi: add ptest support
Date: Tue, 12 May 2026 17:16:02 +0200 [thread overview]
Message-ID: <DIGSPNC40V0B.325NZ64GRFWZL@bootlin.com> (raw)
In-Reply-To: <GV2P189MB3005EFC4E16B3BD9CA42F3C6FE392@GV2P189MB3005.EURP189.PROD.OUTLOOK.COM>
On Tue May 12, 2026 at 10:30 AM CEST, Pratik Farkase wrote:
> Hi Mathieu,
>
> I tested v3 on qemux86-64 against current master and was unable to
> reproduce the glib-2.0 locale or multilib symlinks failures.
>
> Could you share the steps or configuration you used to reproduce the
> these two issues? That would help me investigate further.
>
> Best Regards,
> Pratik
>
Hi Pratik,
Regarding the multilib one, I just managed to reproduce it locally:
Using tag oecore/autobuilder.yoctoproject.org/valkyrie/a-full-3808 from
poky-ci-archive git:
https://git.yoctoproject.org/poky-ci-archive/tag/?h=oecore/autobuilder.yoctoproject.org/valkyrie/a-full-3808
Default local.conf template, with these lines added:
PACKAGE_CLASSES = "package_rpm package_deb package_ipk"
OE_FRAGMENTS += 'core/yocto-autobuilder/multilib-x86-lib64'
SANITY_TESTED_DISTROS = ''
OEQA_TESTDISPLAY = ':1'
OE_FRAGMENTS += 'core/yocto-autobuilder/autobuilder core/yocto-autobuilder/autobuilder-resource-constraints'
EXTRA_IMAGE_FEATURES ?= 'allow-empty-password empty-root-password allow-root-login'
OE_FRAGMENTS += 'machine/qemux86 distro/poky'
Then:
bitbake lib64-core-image-sato-sdk
...
ERROR: lib64-core-image-sato-sdk-1.0-r0 do_rootfs: Could not invoke dnf. Command '...' returned 1:
...
Running transaction check
Transaction check succeeded.
Running transaction test
Error: Transaction test error:
file /usr/bin/g++ conflicts between attempted installs of lib64-g++-symlinks-15.2.0-r0.x86_64 and g++-symlinks-15.2.0-r0.core2_32
file /usr/bin/cpp conflicts between attempted installs of cpp-symlinks-15.2.0-r0.core2_32 and lib64-cpp-symlinks-15.2.0-r0.x86_64
file /usr/bin/gcc conflicts between attempted installs of lib64-gcc-symlinks-15.2.0-r0.x86_64 and gcc-symlinks-15.2.0-r0.core2_32
I will try to reproduce the selftest failures.
Thanks,
Mathieu
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2026-05-12 15:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-07 8:52 [OE-core][PATCH v1] libffi: add ptest support Pratik Farkase
2026-05-08 10:24 ` [OE-core][PATCH v2] " Pratik Farkase
2026-05-08 11:25 ` Marko, Peter
2026-05-08 11:38 ` Pratik Farkase
2026-05-08 11:36 ` [OE-core][PATCH v3] " Pratik Farkase
2026-05-11 6:09 ` Mathieu Dubois-Briand
2026-05-11 9:00 ` Pratik Farkase
2026-05-11 12:25 ` Mathieu Dubois-Briand
2026-05-12 8:30 ` Pratik Farkase
2026-05-12 15:16 ` Mathieu Dubois-Briand [this message]
2026-05-13 5:33 ` Mathieu Dubois-Briand
2026-05-13 8:27 ` Pratik Farkase
2026-05-13 11:31 ` Mathieu Dubois-Briand
2026-05-13 13:30 ` Pratik Farkase
2026-05-13 13:27 ` [OE-core][PATCH v4] " Pratik Farkase
2026-05-20 16:02 ` Ross Burton
2026-05-21 8:30 ` Pratik Farkase
2026-05-25 9:30 ` [OE-core][PATCH v5] " Pratik Farkase
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=DIGSPNC40V0B.325NZ64GRFWZL@bootlin.com \
--to=mathieu.dubois-briand@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=pratik.farkase@ericsson.com \
--cc=pratik.farkase@est.tech \
/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