From: David Gibson <david@gibson.dropbear.id.au>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-ppc@nongnu.org,
"Andreas Färber" <afaerber@suse.de>,
"Alexander Graf" <agraf@suse.de>
Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH] PPC: Fail configure when libfdt is not available
Date: Fri, 21 Oct 2011 14:34:28 +1100 [thread overview]
Message-ID: <20111021033428.GB6826@truffala.fritz.box> (raw)
In-Reply-To: <4EA06A01.5080806@redhat.com>
On Thu, Oct 20, 2011 at 08:35:45PM +0200, Gerd Hoffmann wrote:
> Hi,
>
> > If there are build problems with libfdt on any platform let me know
> > about them. I would like it to build clean as widely as possible, but
> > I don't have that great a diversity of build environments, so I have
> > to reply on bug reports.
>
> Fails to build on RHEL-5:
>
> CC convert-dtsv0-lexer.lex.o
> cc1: warnings being treated as errors
> convert-dtsv0-lexer.lex.c:693: warning: no previous prototype for ‘yylex’
> make: *** [convert-dtsv0-lexer.lex.o] Error 1
This one I can work around, but there's probably not much point because...
> Removing -Werror from the Makefile gets me a bit further:
>
> CC dtc-lexer.lex.o
> dtc-lexer.lex.c:683: warning: no previous prototype for ‘yylex’
> dtc-lexer.l: In function ‘push_input_file’:
> dtc-lexer.l:192: warning: implicit declaration of function
> ‘yypush_buffer_state’
> dtc-lexer.l:192: warning: nested extern declaration of ‘yypush_buffer_state’
> dtc-lexer.l: In function ‘pop_input_file’:
> dtc-lexer.l:201: warning: implicit declaration of function
> ‘yypop_buffer_state’
> dtc-lexer.l:201: warning: nested extern declaration of ‘yypop_buffer_state’
> CC dtc-parser.tab.o
> LD dtc
> dtc-lexer.lex.o: In function `push_input_file':
> /home/buildbot/git/dtc/dtc-lexer.l:192: undefined reference to
> `yypush_buffer_state'
> dtc-lexer.lex.o: In function `pop_input_file':
> /home/buildbot/git/dtc/dtc-lexer.l:201: undefined reference to
> `yypop_buffer_state'
> collect2: ld returned 1 exit status
> make: *** [dtc] Error 1
...this is harder. I do rely fairly heavily on the lex multiple input
buffer support for processing includes. I'm not sure when that went
in, but obviously after flex 2.5.4.
I could rewrite to not rely on the flex stuff and do it myself, but it
would be non-trivial, so I'm afraid that fix won't happen particularly
soon.
> I guess the flex version shipped with RHEL-5 is too old.
>
> $ rpm -qf $(which lex)
> flex-2.5.4a-41.fc6
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
next prev parent reply other threads:[~2011-10-21 3:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-18 0:18 [Qemu-devel] [PATCH] PPC: Fail configure when libfdt is not available Alexander Graf
2011-10-18 6:45 ` Paolo Bonzini
2011-10-18 19:26 ` Richard Henderson
2011-10-19 6:09 ` Paolo Bonzini
2011-10-18 8:55 ` Andreas Färber
2011-10-18 9:02 ` Alexander Graf
2011-10-18 18:30 ` Blue Swirl
2011-10-19 2:08 ` Alexander Graf
2011-10-18 11:37 ` [Qemu-devel] [Qemu-ppc] " David Gibson
2011-10-20 18:35 ` Gerd Hoffmann
2011-10-21 3:34 ` David Gibson [this message]
2011-10-21 7:11 ` Gerd Hoffmann
2011-10-21 7:34 ` Paolo Bonzini
2011-10-24 2:22 ` David Gibson
2011-10-18 9:47 ` [Qemu-devel] " Peter Maydell
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=20111021033428.GB6826@truffala.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.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;
as well as URLs for NNTP newsgroup(s).