From: Ross Burton <Ross.Burton@arm.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH 5/7] class/pkgconfig: use pkgconf instead of pkgconfig
Date: Sat, 21 Mar 2026 11:59:39 +0000 [thread overview]
Message-ID: <19151BEF-3A4C-4FAE-BB26-3FF8FDF17FFB@arm.com> (raw)
In-Reply-To: <CAMKF1sorLiSe3ip43iPs1vQrfO1LBr5D7BuvvyfEmH6KKCRF2g@mail.gmail.com>
On 21 Mar 2026, at 01:40, Khem Raj <raj.khem@gmail.com> wrote:
>
> FWIW there are two recipes in meta-oe which are regressing with this
>
> xmlsec1 and protobuf
>
> https://autobuilder.yoctoproject.org/valkyrie/api/v2/logs/5941365/raw_inline
The protobuf change is because there’s some frankly horrifying sedding of .pc files which I’m surprised survived the recent changes to how pkgconfig.bbclass works. There’s got to be a better way to do this.
The xmlsec failure looks similar.
I can look at these on Monday and try and sort out the mess.
Ross
next prev parent reply other threads:[~2026-03-21 12:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-20 12:27 [PATCH 1/7] sstate/relocatable: remove manual relocation of .pc files Ross Burton
2026-03-20 12:27 ` [PATCH 2/7] pkgconf: inherit pkgconfig Ross Burton
2026-03-20 12:27 ` [PATCH 3/7] pkgconf: ensure pkgconf-native doesn't try and look on the host Ross Burton
2026-03-20 12:27 ` [PATCH 4/7] pkgconf: minimise wrapper Ross Burton
2026-03-20 12:27 ` [PATCH 5/7] class/pkgconfig: use pkgconf instead of pkgconfig Ross Burton
2026-03-21 1:40 ` [OE-core] " Khem Raj
2026-03-21 11:59 ` Ross Burton [this message]
2026-03-25 0:05 ` Dmitry Baryshkov
2026-03-25 0:32 ` [OE-core] " Khem Raj
2026-03-20 12:27 ` [PATCH 6/7] pkgconfig: remove Ross Burton
2026-03-20 12:27 ` [PATCH 7/7] layer.conf: update pkgconfig-native exclusions to pkgconf-native Ross Burton
2026-03-20 12:46 ` Patchtest results for " patchtest
2026-03-20 12:48 ` [OE-core] [PATCH 1/7] sstate/relocatable: remove manual relocation of .pc files 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=19151BEF-3A4C-4FAE-BB26-3FF8FDF17FFB@arm.com \
--to=ross.burton@arm.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.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