From: "Khem Raj" <raj.khem@gmail.com>
To: Ross Burton <ross@burtonini.com>
Cc: Alexander Kanavin <alex.kanavin@gmail.com>,
OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH v2 1/3] meson: fix native/host confusion in gobject-introspection
Date: Fri, 26 Mar 2021 11:48:39 -0700 [thread overview]
Message-ID: <CAMKF1sqMj-d-Dj-Kq3N5gAJBZtFDzGY=Rcc2J9uKD_gA-i9e8g@mail.gmail.com> (raw)
In-Reply-To: <CAAnfSTvXHyX_MvHbtpcUso92K=DQT1_7hMwAGCDPJ9RMW0zVPg@mail.gmail.com>
I am seeing some failures
https://errors.yoctoproject.org/Errors/Details/574541/
On Thu, Mar 25, 2021 at 12:08 PM Ross Burton <ross@burtonini.com> wrote:
>
> On Thu, 25 Mar 2021 at 18:15, Alexander Kanavin <alex.kanavin@gmail.com> wrote:
> > I don't think I fully understand this. Is g-i in meson projects already broken for a while (there was a bit of refactor in the latest meson version, which I tested, but perhaps not well enough), or is this necessary for the other patches in your set?
>
> I just sent a mail which sort-of answers this question without seeing it.
>
> Basically, the change is that Meson now knows that it should call
> pkg-config-native for native pkgconfig lookups. Before, it was using
> pkg-config.
>
> As far as I can tell there is very little code which hits that
> codepath, so we didn't notice. When setting pkgconfig-native
> correctly, this broke.
>
> Ross
>
>
>
next prev parent reply other threads:[~2021-03-26 18:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-25 17:38 [PATCH v2 1/3] meson: fix native/host confusion in gobject-introspection Ross Burton
2021-03-25 17:39 ` [PATCH v2 2/3] bitbake.conf: ensure BUILD_* tools match target tools Ross Burton
2021-03-25 17:39 ` [PATCH v2 3/3] meson: use native-file instead of environment variables Ross Burton
2021-03-25 18:15 ` [OE-core] [PATCH v2 1/3] meson: fix native/host confusion in gobject-introspection Alexander Kanavin
2021-03-25 19:07 ` Ross Burton
2021-03-26 18:48 ` Khem Raj [this message]
2021-03-29 9:25 ` Ross Burton
2021-03-29 15:26 ` Khem Raj
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='CAMKF1sqMj-d-Dj-Kq3N5gAJBZtFDzGY=Rcc2J9uKD_gA-i9e8g@mail.gmail.com' \
--to=raj.khem@gmail.com \
--cc=alex.kanavin@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross@burtonini.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.