From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [oe-commits] [openembedded-core] 08/08: json-glib: update to 1.4.2
Date: Mon, 22 Jan 2018 15:33:41 +0200 [thread overview]
Message-ID: <61b45636-ba1a-92d4-1932-1084db0a54e0@linux.intel.com> (raw)
In-Reply-To: <CA+chaQcum56vWjDunvXB-iWHV097SyLUiQusOVwgTkisPzQOTA@mail.gmail.com>
On 01/19/2018 07:59 PM, Martin Jansa wrote:
> I have gobject-introspection-data in DISTRO_FEATURES_BACKFILL_CONSIDERED.
>
> I am able to reproduce this with nodistro after adding:
> DISTRO_FEATURES_remove = "gobject-introspection-data"
> or the same to DISTRO_FEATURES_BACKFILL_CONSIDERED.
>
> This one is with require conf/distro/include/security_flags.inc
> http://errors.yoctoproject.org/Errors/Details/164873/
> <http://errors.yoctoproject.org/Errors/Details/164873/>
>
> this one is without security_flags.inc:
> http://errors.yoctoproject.org/Errors/Details/164874/
>
> The older version was building fine with gobject-introspection disabled.
Upstream has renamed all the configuration options, and then renamed
them again. At the same time, meson stays quiet about configuration
options that don't exist, and so we don't have an automatic way to catch
such regressions.
https://github.com/GNOME/json-glib/commits/master/meson_options.txt
I'll fix the recipe.
Alex
next prev parent reply other threads:[~2018-01-22 13:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <151627986059.9023.14010623458474127186@git.openembedded.org>
[not found] ` <20180118125101.2F92F235ED3@git.openembedded.org>
2018-01-19 13:58 ` [oe-commits] [openembedded-core] 08/08: json-glib: update to 1.4.2 Martin Jansa
2018-01-19 14:02 ` Burton, Ross
2018-01-19 14:06 ` Martin Jansa
2018-01-19 14:12 ` Burton, Ross
2018-01-19 15:07 ` Alexander Kanavin
2018-01-19 17:59 ` Martin Jansa
2018-01-22 13:33 ` Alexander Kanavin [this message]
2018-01-24 2:26 ` Yi Zhao
2018-01-24 2:31 ` Yi Zhao
2018-01-24 8:19 ` Martin Jansa
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=61b45636-ba1a-92d4-1932-1084db0a54e0@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
/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.