From: Khem Raj <raj.khem@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: [meta-gnome][PATCH 6/6] libgnome-keyring, gnome-keyring: Add build dep on glib-2.0-native
Date: Mon, 19 Mar 2018 21:00:00 -0700 [thread overview]
Message-ID: <20180320040000.29408-6-raj.khem@gmail.com> (raw)
In-Reply-To: <20180320040000.29408-1-raj.khem@gmail.com>
Fixes
run.do_configure.39296: line 176: glib-gettextize: command not found
Signed-off-by: Khem Raj <raj.khem@gmail.com>
---
meta-gnome/recipes-gnome/gnome-keyring/gnome-keyring_2.32.1.bb | 2 +-
meta-gnome/recipes-gnome/gnome-keyring/libgnome-keyring_2.32.0.bb | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/meta-gnome/recipes-gnome/gnome-keyring/gnome-keyring_2.32.1.bb b/meta-gnome/recipes-gnome/gnome-keyring/gnome-keyring_2.32.1.bb
index 9d85c651c..5a9ca5f6e 100644
--- a/meta-gnome/recipes-gnome/gnome-keyring/gnome-keyring_2.32.1.bb
+++ b/meta-gnome/recipes-gnome/gnome-keyring/gnome-keyring_2.32.1.bb
@@ -21,7 +21,7 @@ SRC_URI += "file://egg-asn1x.patch \
file://musl.patch \
"
-DEPENDS = "gtk+ libgcrypt libtasn1 libtasn1-native gconf ${@bb.utils.contains('DISTRO_FEATURES', 'pam', 'libpam', '', d)} intltool-native"
+DEPENDS = "gtk+ libgcrypt libtasn1 libtasn1-native gconf ${@bb.utils.contains('DISTRO_FEATURES', 'pam', 'libpam', '', d)} intltool-native glib-2.0-native"
RDEPENDS_${PN} = "libgnome-keyring glib-2.0-utils"
LDFLAGS += "-lgmodule-2.0"
diff --git a/meta-gnome/recipes-gnome/gnome-keyring/libgnome-keyring_2.32.0.bb b/meta-gnome/recipes-gnome/gnome-keyring/libgnome-keyring_2.32.0.bb
index e24188232..7e9de5026 100644
--- a/meta-gnome/recipes-gnome/gnome-keyring/libgnome-keyring_2.32.0.bb
+++ b/meta-gnome/recipes-gnome/gnome-keyring/libgnome-keyring_2.32.0.bb
@@ -13,7 +13,7 @@ PR = "r3"
inherit gnomebase gtk-doc
-DEPENDS = "dbus libgcrypt glib-2.0 intltool-native"
+DEPENDS = "dbus libgcrypt glib-2.0 glib-2.0-native intltool-native"
SRC_URI[archive.md5sum] = "c42b2ca66204835d901d3dbfc1fa5ae6"
SRC_URI[archive.sha256sum] = "56388c0d81ddfdb57d30e4963c83ecc1c18498aab99395420e0fff69929a0f0c"
--
2.16.2
prev parent reply other threads:[~2018-03-20 4:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-20 3:59 [meta-networking][PATCH 1/6] ndisc6: gold does not work for risc-v here Khem Raj
2018-03-20 3:59 ` [meta-oe][PATCH 2/6] krb5: Add -D_REENTRANT -pthread to CFLAGS on risc-v Khem Raj
2018-03-20 3:59 ` [meta-oe][PATCH 3/6] krb5: Correctly specify configure option --with-crypto-impl Khem Raj
2018-03-20 3:59 ` [meta-networking][PATCH 4/6] waf-cross-answers: Add cross-answers-riscv64.txt Khem Raj
2018-03-20 3:59 ` [meta-oe][PATCH 5/6] libqb: Upgrade to 1.0.3 Khem Raj
2018-03-31 6:04 ` Martin Jansa
2018-06-13 7:08 ` Martin Jansa
2018-06-13 13:42 ` Khem Raj
2018-03-20 4:00 ` Khem Raj [this message]
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=20180320040000.29408-6-raj.khem@gmail.com \
--to=raj.khem@gmail.com \
--cc=openembedded-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).