Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Andrei Gherzan <andrei@gherzan.ro>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] eglibc: Add missing dependency of gettext-native
Date: Sun, 10 Feb 2013 00:03:51 +0000	[thread overview]
Message-ID: <1360454631.10722.130.camel@ted> (raw)
In-Reply-To: <1360431352-29452-1-git-send-email-andrei@gherzan.ro>

On Sat, 2013-02-09 at 19:35 +0200, Andrei Gherzan wrote:
> /bin/bash: msgfmt: command not found
> | make[2]: *** [be.mo] Error 127
> 
> Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
> ---
>  meta/recipes-core/eglibc/eglibc_2.17.bb |    4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/meta/recipes-core/eglibc/eglibc_2.17.bb b/meta/recipes-core/eglibc/eglibc_2.17.bb
> index fb49ac4..03e0ea4 100644
> --- a/meta/recipes-core/eglibc/eglibc_2.17.bb
> +++ b/meta/recipes-core/eglibc/eglibc_2.17.bb
> @@ -1,8 +1,8 @@
>  require eglibc.inc
>  
> -PR = "r3"
> +PR = "r4"
>  
> -DEPENDS += "gperf-native kconfig-frontends-native"
> +DEPENDS += "gperf-native kconfig-frontends-native gettext-native"
>  
>  SRC_URI = "http://downloads.yoctoproject.org/releases/eglibc/eglibc-${PV}-svnr22064.tar.bz2 \
>             file://eglibc-svn-arm-lowlevellock-include-tls.patch \

This will seriously hurt build times :(

I'm not saying this is wrong but I would like to understand how we've
managed for as long without it...

Cheers,

Richard




  reply	other threads:[~2013-02-10  0:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-09 17:35 [PATCH 1/1] eglibc: Add missing dependency of gettext-native Andrei Gherzan
2013-02-10  0:03 ` Richard Purdie [this message]
2013-02-10  9:44   ` Andrei Gherzan

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=1360454631.10722.130.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=andrei@gherzan.ro \
    --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