This is the mail archive of the
binutils@sourceware.org
mailing list for the binutils project.
Re: New version of flex and compiling binutils
- From: NightStrike <nightstrike at gmail dot com>
- To: "Ben Elliston" <bje at au1 dot ibm dot com>
- Cc: "Nick Clifton" <nickc at redhat dot com>, Binutils <binutils at sourceware dot org>
- Date: Mon, 3 Dec 2007 15:26:42 -0500
- Subject: Re: New version of flex and compiling binutils
- References: <b609cb3b0710020412v32ee2031l464b3b8f6721f854@mail.gmail.com> <4704F529.5010203@redhat.com> <b609cb3b0710040943r4aa2800cle8892c9431a88235@mail.gmail.com> <47051B0B.6080601@redhat.com> <b609cb3b0710040958l3f1583f6s308af2b35275626d@mail.gmail.com> <1191820149.23720.6.camel@localhost>
On 10/8/07, Ben Elliston <bje@au1.ibm.com> wrote:
> On Thu, 2007-10-04 at 12:58 -0400, NightStrike wrote:
>
> > Yes it does. Thank you very much! I will hop over to their project
> > immediately and see what I can do.
>
> I took a crack at getting these bugs fixed, but was not successful. I
> can't remember now what happened, but my report obviously didn't lead to
> the problem being fixed. :-)
>
> The other issue I ran into is that some developers believe that recent
> versions of flex are unsuitable for use in GCC/binutils. Thus, fixing
> these code generation problems in an even more recent version of flex
> would be futile if GCC/binutils are unwilling to adopt that version at a
> minimum.
>
> However, don't let me stop you trying -- those warnings drive me
> nuts. :-)
This took a while due to family health emergencies, but I have posted
to the flex mailing list, received a wonderful reply, and filed a bug
report. Looks like progress shall ensue!
flex bug report:
http://sourceforge.net/tracker/index.php?func=detail&aid=1843615&group_id=97492&atid=618177
flex mailing list message:
http://sourceforge.net/mailarchive/forum.php?thread_name=b609cb3b0712031121t1aec3a8bpcb559a2f6f99d8b%40mail.gmail.com&forum_name=flex-help
I hope that helps.