From: Johns Daniel <johns.daniel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Jon Loeliger <jdl-CYoMK+44s/E@public.gmane.org>
Cc: devicetree-discuss-mnsaURCQ41sdnm+yROfE0A@public.gmane.org
Subject: Re: Cannot compile the DTC itself
Date: Thu, 2 Apr 2009 14:46:59 -0500 [thread overview]
Message-ID: <ba5d9360904021246g72afa876uc69ce188040b1e71@mail.gmail.com> (raw)
In-Reply-To: <E1LpSjM-0005us-Nw-CYoMK+44s/E@public.gmane.org>
On Thu, Apr 2, 2009 at 2:37 PM, Jon Loeliger <jdl-CYoMK+44s/E@public.gmane.org> wrote:
>> I get similar errors for dtc-v1.1.0 and dtc-v1.2.0:
>>
>> ...
>> CC dtc-lexer.lex.o
>> dtc-lexer.lex.c: In function `yylex':
>> dtc-lexer.lex.c:762: warning: label `find_rule' defined but not used
>> dtc-lexer.l: At top level:
>> dtc-lexer.lex.c:1870: warning: 'yy_flex_realloc' defined but not used
>> CC dtc-parser.tab.o
>> dtc-parser.tab.c: In function `yyparse':
>> dtc-parser.tab.c:1105: warning: implicit declaration of function `YYRHSLOC'
>> dtc-parser.tab.c:1105: error: request for member `first_line' in
>
> What version of flex are you using?
flex version 2.5.4 (the latest for my Linux distribution)
> Have you tried to install a recent version of flex?
No, not yet.
Thanks for the info! I suspected that, but could not find any evidence
to support my theory.
next prev parent reply other threads:[~2009-04-02 19:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-02 19:07 Cannot compile the DTC itself Johns Daniel
[not found] ` <ba5d9360904021207j32a13e43i9b6347147ccf7563-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-04-02 19:37 ` Jon Loeliger
[not found] ` <E1LpSjM-0005us-Nw-CYoMK+44s/E@public.gmane.org>
2009-04-02 19:46 ` Johns Daniel [this message]
[not found] ` <ba5d9360904021246g72afa876uc69ce188040b1e71-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-04-02 22:01 ` David Gibson
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=ba5d9360904021246g72afa876uc69ce188040b1e71@mail.gmail.com \
--to=johns.daniel-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=devicetree-discuss-mnsaURCQ41sdnm+yROfE0A@public.gmane.org \
--cc=jdl-CYoMK+44s/E@public.gmane.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