Re: [PATCH v13 09/10] rpm: Fix pkgconfig() Provides missing in cross-built RPMs

["Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>]

On Tue Aug 11, 2026 at 4:19 PM CEST, Mathieu Dubois-Briand wrote:
> On Mon Aug 10, 2026 at 6:52 AM CEST, Sumanth Gavini wrote:
>> * Added 0002-pkgconfigdeps.sh-Unset-cross-compilation-PKG_CONFIG-v.patch
>>   - rpm 6's internal dependency generator runs pkgconfigdeps.sh during
>>     rpmbuild, but OE's cross-build environment exports PKG_CONFIG_SYSROOT_DIR
>>     which causes pkg-config --print-provides to silently fail on .pc files
>>     in the package buildroot.
>>
>>     Unset cross-compilation PKG_CONFIG_* variables in pkgconfigdeps.sh so
>>     that pkgconfig() Provides/Requires are correctly generated.
>>
>>     Without this fix, do_rootfs fails with errors like:
>>     nothing provides pkgconfig(ogg) needed by flac-dev
>>
>> Signed-off-by: Sumanth Gavini <sumanth.gavini@windriver.com>
>> ---
>
> Hi Sumanth,
>
> Thanks for the new version.
>
> This looks better, at least for the dnf install errors. Yet we still
> have errors when reusing sstate-cache, as recipes generating pkgconfig
> should be rebuilt, but their signatures did not change:
>
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/4/builds/4377
>
> I made some horrible hack in my branch to change the PR of many
> recipes, and the build now succeeds. I only tested one configuration,
> but we can expect similar results on the other ones.
>
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/4/builds/4386
>
> So, depending on how you address Ross comment, you might need to make
> sure recipes signature is going to change.
>
> We also had some selftest errors: I will investigate a bit further and
> come back to you.
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/35/builds/4525
>
> Thanks,
> Mathieu

So, talking about failed selftests. We can see three failing tests on
the autobuilder:

2026-08-11 15:19:21,651 - oe-selftest - INFO - debuginfod.Debuginfod.test_debuginfod_qemu (subunit.RemotedTestCase)
2026-08-11 15:19:21,652 - oe-selftest - INFO -  ... FAIL
...
2026-08-11 16:53:01,397 - oe-selftest - INFO - sdk.SDKTests.test_sdk_manifests (subunit.RemotedTestCase)
2026-08-11 16:53:01,401 - oe-selftest - INFO -  ... FAIL
...
2026-08-11 16:55:44,191 - oe-selftest - INFO - sdk.SDKTests.test_sdk_runqemu (subunit.RemotedTestCase)
2026-08-11 16:55:44,191 - oe-selftest - INFO -  ... FAIL

https://autobuilder.yoctoproject.org/valkyrie/#/builders/35/builds/4537

The first one is easy to reproduce locally. Basically, I have this in my
local.conf:
SDKMACHINE = "x86_64"
PACKAGE_CLASSES = "package_rpm package_deb package_ipk"
INHERIT += 'image-buildinfo'
IMAGE_BUILDINFO_VARS:append = ' IMAGE_BASENAME IMAGE_NAME'
SANITY_TESTED_DISTROS = ''
OEQA_TESTDISPLAY = ':1'
EXTRA_IMAGE_FEATURES ?= 'allow-empty-password empty-root-password allow-root-login'
OE_FRAGMENTS += 'distro/poky'

Then you can run:
oe-selftest -v -r debuginfod.Debuginfod.test_debuginfod_qemu

I was not able to reproduce the two other ones locally so far. It looks
like another pkgconfig issue. I suggest we focus on other issues right
now, hopefully the SDKTests failures will be gone with your next
changes.

Thanks,
Mathieu

-- 
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com