Bug 1306000
| Summary: | Bison is out of date | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Josh Marshall <jrmarsha> |
| Component: | bison | Assignee: | Patsy Griffin <pfrankli> |
| Status: | CLOSED ERRATA | QA Contact: | Martin Cermak <mcermak> |
| Severity: | low | Docs Contact: | Vladimír Slávik <vslavik> |
| Priority: | unspecified | ||
| Version: | 7.2 | CC: | law, mcermak, mnewsome, pfrankli |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| 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`.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-08-01 18:03:07 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1390370 | ||
|
Description
Josh Marshall
2016-02-09 19:18:53 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. https://access.redhat.com/errata/RHBA-2017:1899 |