[Octave-bug-tracker] [bug #55613] Build failure with bison 3.3.1

[Mike Miller]

Update of bug #55613 (project octave):

                  Status:               Confirmed => Patch Submitted        

    _______________________________________________________

Follow-up Comment #5:

I'm attaching the change I want to make on the stable branch, please comment
if anyone has any objections. I've tested this with bison 3.2.4 and 3.3.1,
both work for me, and I believe this change is both safe and the most
appropriate solution.

Rationale - I did a bit more research into the recent change and the
relationship between autoconf and bison. The bison 3.0 release notes
specifically mention that a future version of autoconf will stop calling bison
with the "-y" option. Until then, for all current versions of autoconf, users
should call bison with "-Wno-yacc" added to AM_YFLAGS to silence warnings when
using bison-specific directives. This option is safe for any version of bison
2.5 and newer.

Version 3.0 is also the first version to support the current "%define
api.prefix {FOO}" syntax that Octave tests for and requires.

GNU bison 2.5 was released May 2011.

GNU bison 3.0 was released July 2013.

All supported versions of Debian and Ubuntu, even the old LTS versions (from
2014-2015), have bison 3.0 or newer.

CentOS 7 has bison 3.0.4, CentOS 6 has bison 2.4.1.

(file #46152)
    _______________________________________________________

Additional Item Attachment:

File name: bug55613.patch                 Size:2 KB
    <https://savannah.gnu.org/file/bug55613.patch?file_id=46152>



    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?55613>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/