From: Gerd Hoffmann <kraxel@redhat.com>
To: "Andreas Färber" <afaerber@suse.de>,
"Alexander Graf" <agraf@suse.de>,
qemu-ppc@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH] PPC: Fail configure when libfdt is not available
Date: Fri, 21 Oct 2011 09:11:28 +0200 [thread overview]
Message-ID: <4EA11B20.3050800@redhat.com> (raw)
In-Reply-To: <20111021033428.GB6826@truffala.fritz.box>
Hi,
>> 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.
For the record: Updating flex to 2.5.35 made dtc build fine on RHEL-5.
cheers,
Gerd
next prev parent reply other threads:[~2011-10-21 7:11 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
2011-10-21 7:11 ` Gerd Hoffmann [this message]
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=4EA11B20.3050800@redhat.com \
--to=kraxel@redhat.com \
--cc=afaerber@suse.de \
--cc=agraf@suse.de \
--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).