From: Phil Blundell <pb@pbcl.net>
To: oe-core <openembedded-core@lists.openembedded.org>
Subject: [PATCH] eglibc: Add gettext-native to DEPENDS
Date: Tue, 23 Apr 2013 17:44:43 +0100 [thread overview]
Message-ID: <1366735483.5732.18.camel@phil-desktop.brightsign> (raw)
Otherwise you get:
| msgfmt -o be.mo be.po
| msgfmt -o bg.mo bg.po
| msgfmt -o ca.mo ca.po
| /bin/bash: msgfmt: command not found
| make[2]: *** [be.mo] Error 127
| make[2]: *** Waiting for unfinished jobs....
| /bin/bash: msgfmt: command not found
| make[2]: *** [ca.mo] Error 127
| /bin/bash: msgfmt: command not found
| make[2]: *** [bg.mo] Error 127
if msgfmt isn't available in the host environment.
Signed-off-by: Phil Blundell <philb@gnu.org>
---
meta/recipes-core/eglibc/eglibc.inc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-core/eglibc/eglibc.inc b/meta/recipes-core/eglibc/eglibc.inc
index 1e04197..38d8c44 100644
--- a/meta/recipes-core/eglibc/eglibc.inc
+++ b/meta/recipes-core/eglibc/eglibc.inc
@@ -33,7 +33,7 @@ siteconfig_do_siteconfig_gencache_prepend = " \
"
# nptl needs unwind support in gcc, which can't be built without glibc.
-DEPENDS = "virtual/${TARGET_PREFIX}gcc-initial linux-libc-headers virtual/${TARGET_PREFIX}libc-initial"
+DEPENDS = "virtual/${TARGET_PREFIX}gcc-initial linux-libc-headers virtual/${TARGET_PREFIX}libc-initial gettext-native"
# nptl needs libgcc but dlopens it, so our shlibs code doesn't detect this
#RDEPENDS_${PN} += "${@['','libgcc']['nptl' in '${GLIBC_ADDONS}']}"
PROVIDES = "virtual/libc virtual/${TARGET_PREFIX}libc-for-gcc"
--
1.7.10.4
next reply other threads:[~2013-04-23 17:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-23 16:44 Phil Blundell [this message]
2013-04-23 21:45 ` [PATCH] eglibc: Add gettext-native to DEPENDS Richard Purdie
2013-04-24 7:58 ` Phil Blundell
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=1366735483.5732.18.camel@phil-desktop.brightsign \
--to=pb@pbcl.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox