From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] eglibc-initial-2.16: add kconfig-frontends-native to depends
Date: Mon, 10 Sep 2012 16:58:27 +0100 [thread overview]
Message-ID: <1347292707.29562.3.camel@ted> (raw)
In-Reply-To: <1347285878-14778-1-git-send-email-Martin.Jansa@gmail.com>
On Mon, 2012-09-10 at 16:04 +0200, Martin Jansa wrote:
> * fixes:
> | make[1]: Entering directory `/OE/shr-core/tmp-eglibc/work/armv5te-oe-linux-gnueabi/eglibc-initial-2.16-r8+svnr20393/eglibc-2_16/libc'
> | make[1]: *** No rule to make target `/OE/shr-core/tmp-eglibc/sysroots/x86_64-linux/usr/bin/conf', needed by `config'. Stop.
> | make[1]: Leaving directory `/OE/shr-core/tmp-eglibc/work/armv5te-oe-linux-gnueabi/eglibc-initial-2.16-r8+svnr20393/eglibc-2_16/libc'
>
> * it's because, eglibc-initial.inc overwrites DEPENDS from eglibc_2.16.bb
> $ grep DEPENDS eglibc_2.16.bb
> DEPENDS += "gperf-native kconfig-frontends-native"
> $ grep DEPENDS eglibc-initial.inc
> DEPENDS = "linux-libc-headers virtual/${TARGET_PREFIX}gcc-initial"
>
> and it's included after eglibc_2.16.bb
> $ head -n 3 eglibc-initial_2.16.bb
> require eglibc_${PV}.bb
> require eglibc-initial.inc
>
> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
> ---
> meta/recipes-core/eglibc/eglibc-initial_2.16.bb | 2 ++
> 1 file changed, 2 insertions(+)
Merged to master, thanks.
Richard
prev parent reply other threads:[~2012-09-10 16:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20120910120835.C24EF10348@opal>
2012-09-10 12:45 ` [oe-commits] Khem Raj : eglibc-2.16: Add kconfig infrastructure Martin Jansa
2012-09-10 14:04 ` [PATCH] eglibc-initial-2.16: add kconfig-frontends-native to depends Martin Jansa
2012-09-10 15:58 ` Richard Purdie [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=1347292707.29562.3.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=martin.jansa@gmail.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