From: Joshua Lock <joshua.g.lock@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] glib-2.0: Re-add the gettext depend
Date: Thu, 18 Jan 2018 19:23:01 +0000 [thread overview]
Message-ID: <cb001244-b8fa-1425-54fa-98d65d4d43fb@linux.intel.com> (raw)
In-Reply-To: <20180118191245.9490-1-alistair.francis@xilinx.com>
On 18/01/18 19:12, Alistair Francis wrote:
> Commit "glib-2.0: rationalise build dependencies"
> (8b0ca0cb54c91611213556bdb99316d5e7ac5b3b) broke mingw glib builds with
> the following error:
>
> This patch fixes the issue by re-adding the gettext dependency.
>
> Signed-off-by: Alistair Francis <alistair.francis@xilinx.com>
> ---
> meta/recipes-core/glib-2.0/glib.inc | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/meta/recipes-core/glib-2.0/glib.inc b/meta/recipes-core/glib-2.0/glib.inc
> index 354d95cfe3..e6997ae88f 100644
> --- a/meta/recipes-core/glib-2.0/glib.inc
> +++ b/meta/recipes-core/glib-2.0/glib.inc
> @@ -24,6 +24,7 @@ DEPENDS = "glib-2.0-native \
> virtual/libiconv \
> libffi \
> zlib \
> + gettext \
If this is only required for mingw we should add it in a mingw override,
something like (untested):
DEPENDS_mingw32 += "gettext"
That way we:
a) know that it's a mingw dependency (and to test that toolchain before
removing)
b) don't bloat the DEPENDS where gettext isn't a strict requirement.
> ${@bb.utils.contains('PTEST_ENABLED', '1', 'dbus', '', d)}"
>
> PACKAGES += "${PN}-codegen ${PN}-utils"
>
next prev parent reply other threads:[~2018-01-18 19:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-18 19:12 [PATCH] glib-2.0: Re-add the gettext depend Alistair Francis
2018-01-18 19:23 ` Joshua Lock [this message]
2018-01-18 19:28 ` Alistair Francis
2018-01-18 20:02 ` Burton, Ross
2018-01-19 1:06 ` Alistair Francis
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=cb001244-b8fa-1425-54fa-98d65d4d43fb@linux.intel.com \
--to=joshua.g.lock@linux.intel.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.