From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Eric Bénard" <eric@eukrea.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH/RFC] autotools: handle dependency on intltool-native
Date: Mon, 23 Sep 2013 12:24:17 +0100 [thread overview]
Message-ID: <1379935457.18603.215.camel@ted> (raw)
In-Reply-To: <1379923619-27142-1-git-send-email-eric@eukrea.com>
On Mon, 2013-09-23 at 10:06 +0200, Eric Bénard wrote:
> autotools' class can use intltoolize but has no dependency on it
> which can leads to :
> /test/setup-scripts/build/tmp-defaultsetup-eglibc-eglibc/work/cortexa9hf-vfp-neon-oe-linux-gnueabi/gnokii/0.6.31-r0/temp/run.do_configure.7559: line 179: intltoolize: command not found
>
> This patch fix this problem by adding the dependency on
> intltool-native which can be tricky as it triggers
> circular dependencies very easily.
>
> Signed-off-by: Eric Bénard <eric@eukrea.com>
> ---
> meta/classes/autotools.bbclass | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/meta/classes/autotools.bbclass b/meta/classes/autotools.bbclass
> index 883eb06..eb988cb 100644
> --- a/meta/classes/autotools.bbclass
> +++ b/meta/classes/autotools.bbclass
> @@ -16,6 +16,7 @@ def autotools_dep_prepend(d):
> and not bb.data.inherits_class('cross', d) \
> and not d.getVar('INHIBIT_DEFAULT_DEPS', True):
> deps += 'libtool-cross '
> + deps += 'intltool-native '
>
> return deps + 'gnu-config-native '
Its expected that recipes using that add to DEPENDS. Please lets not add
in the dependency for everyone since it isn't actually used in that many
places. Its small details like this which end up causing significant
performance issues :/.
Cheers,
Richard
next prev parent reply other threads:[~2013-09-23 11:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-23 8:06 [PATCH/RFC] autotools: handle dependency on intltool-native Eric Bénard
2013-09-23 11:24 ` Richard Purdie [this message]
2013-09-23 11:53 ` Eric Bénard
2013-09-23 14:34 ` Richard Purdie
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=1379935457.18603.215.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=eric@eukrea.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox