[gstreamer-bugs] [Bug 564361] New: Bison check fails for bison-2.4.1

[GStreamer (bugzilla.gnome.org)]

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=564361

  GStreamer | gstreamer (core) | Ver: 0.10.21
           Summary: Bison check fails for bison-2.4.1
           Product: GStreamer
           Version: 0.10.21
          Platform: Other
        OS/Version: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: gstreamer (core)
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: ulf_gruene at yahoo.de
         QAContact: gstreamer-bugs at lists.sourceforge.net
     GNOME version: 2.23/2.24
   GNOME milestone: Unspecified


Please describe the problem:
The configure script fails when the current version 2.4.1 of bison is
installed.
The last lines of ./configure output are
  checking for perl... /usr/bin/perl
  checking for bison... /usr/bin/bison
  checking bison version 2.4.1 >= 1.875... Argument "^B^D^A" isn't numeric in
numeric lt (<) at - line 1.
  configure: error: no

Just for reference: "bison --version" prints 
bison (GNU Bison) 2.4.1
Written by Robert Corbett and Richard Stallman.

Copyright (C) 2008 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.



Steps to reproduce:
1. Install bison version 2.4.1
2. run ./configure
3. 


Actual results:
configure aborts

Expected results:


Does this happen every time?
yes

Other information:


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=564361.