Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: Yuanjie Huang <Yuanjie.Huang@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] gdb-cross: depends on flex-native and bison-native
Date: Tue, 22 Nov 2016 19:05:36 -0800	[thread overview]
Message-ID: <7CEAD313-1930-44C6-92A5-29E922A3485A@gmail.com> (raw)
In-Reply-To: <20161123020049.22482-1-Yuanjie.Huang@windriver.com>


> On Nov 22, 2016, at 6:00 PM, Yuanjie Huang <Yuanjie.Huang@windriver.com> wrote:
> 
> From: Yuanjie Huang <yuanjie.huang@windriver.com>
> 
> Some source code of gdb is generated with flex or bison. Make both
> dependencies, to avoid compilation failure on host without them.


can you find out which parts those are ? what is it trying to do to need flex/yacc
> 
> Signed-off-by: Yuanjie Huang <yuanjie.huang@windriver.com>
> ---
> meta/recipes-devtools/gdb/gdb-cross.inc | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/meta/recipes-devtools/gdb/gdb-cross.inc b/meta/recipes-devtools/gdb/gdb-cross.inc
> index 5fa7c33..a34223e 100644
> --- a/meta/recipes-devtools/gdb/gdb-cross.inc
> +++ b/meta/recipes-devtools/gdb/gdb-cross.inc
> @@ -1,6 +1,6 @@
> require gdb-common.inc
> 
> -DEPENDS = "expat-native ncurses-native"
> +DEPENDS = "expat-native ncurses-native flex-native bison-native"
> 
> inherit python3native
> 
> -- 
> 2.7.4
> 
> -- 
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core



  reply	other threads:[~2016-11-23  3:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-23  2:00 [PATCH 1/1] gdb-cross: depends on flex-native and bison-native Yuanjie Huang
2016-11-23  3:05 ` Khem Raj [this message]
2016-11-23  3:22   ` Yuanjie Huang
2016-11-23  3:38     ` Khem Raj
2016-11-23  6:49       ` Yuanjie Huang
2016-11-23  6:52         ` Khem Raj

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=7CEAD313-1930-44C6-92A5-29E922A3485A@gmail.com \
    --to=raj.khem@gmail.com \
    --cc=Yuanjie.Huang@windriver.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