From: Yuanjie Huang <yuanjie.huang@windriver.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] gdb-cross: depends on flex-native and bison-native
Date: Wed, 23 Nov 2016 14:49:45 +0800 [thread overview]
Message-ID: <926fbd84-941c-2eeb-d189-27133a6b0688@windriver.com> (raw)
In-Reply-To: <76B00DDD-67D7-467A-84F7-67C0FB25EA62@gmail.com>
On 11/23/2016 11:38 AM, Khem Raj wrote:
> are they regenerating code during configure ?
No, code is generated during compilation. Corresponding c files are not
included in git repo, so these files are always compiled from flex/bison
source files.
>> On Nov 22, 2016, at 7:22 PM, Yuanjie Huang <yuanjie.huang@windriver.com> wrote:
>>
>> Hi Raj,
>>
>> We observed gdb/ada-lex.l is processed by flex while gdb/c-exp.y, gdb/f-exp.y, gdb/go-exp.y and many others are handled by bison. Basically, all language-specific codes in gdb are generated.
>>
>> Best,
>> Yuanjie
>>
>> On 11/23/2016 11:05 AM, Khem Raj wrote:
>>>> 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
next prev parent reply other threads:[~2016-11-23 6:49 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
2016-11-23 3:22 ` Yuanjie Huang
2016-11-23 3:38 ` Khem Raj
2016-11-23 6:49 ` Yuanjie Huang [this message]
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=926fbd84-941c-2eeb-d189-27133a6b0688@windriver.com \
--to=yuanjie.huang@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/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