Bug 1306000 - Bison is out of date
Summary: Bison is out of date
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: bison
Version: 7.2
Hardware: All
OS: Linux
Target Milestone: rc
: ---
Assignee: Patsy Griffin
QA Contact: Martin Cermak
Vladimír Slávik
Depends On:
Blocks: 1390370
TreeView+ depends on / blocked
Reported: 2016-02-09 19:18 UTC by Josh Marshall
Modified: 2017-08-01 18:03 UTC (History)
4 users (show)

Fixed In Version: bison-3.0.4-1.3l7
Doc Type: Rebase: Bug Fixes and Enhancements
Doc Text:
_bison_ rebased to version 3.0.4 The _bison_ package has been upgraded to upstream version 3.0.4, which provides a number of bug fixes and enhancements: * Endless diagnostics caused by caret errors have been fixed. * The "-Werror=CATEGORY" option has been added to treat specified warnings as errors. The warnings do not have to be explicitly activated using the "-W" option. * Many improvements in handling of precedence rules and useless rules. Additionally, the following changes breaking backward compatibility have been introduced: * The following features have been deprecated: `YYFAIL`, `YYLEX_PARAM`, `YYPARSE_PARAM`, `yystype`, `yyltype` * Missing semicolons at the end of actions are no longer automatically added. * To use Bison extensions with the *autoconf* utility versions 2.69 and earlier, pass the option "-Wno-yacc" to `(AM_)YFLAGS`.
Clone Of:
Last Closed: 2017-08-01 18:03:07 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:1899 0 normal SHIPPED_LIVE bison bug fix update 2017-08-01 18:05:23 UTC

Description Josh Marshall 2016-02-09 19:18:53 UTC
Description of problem:
Bison version appears to be on the 2.7 release line rather than the 3.0 line.

How reproducible:

Steps to Reproduce:

Comment 11 errata-xmlrpc 2017-08-01 18:03:07 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.