< Changes
(Rebase binutils to version 2.32) |
(Change target release to F31) |
||
| Line 46: | Line 46: | ||
== Current status == | == Current status == | ||
* Targeted release: Fedora | * Targeted release: Fedora 31 | ||
* Last updated: <!-- this is an automatic macro — you don't need to change this line --> {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}} | * Last updated: <!-- this is an automatic macro — you don't need to change this line --> {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}} | ||
<!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page | <!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page | ||
Latest revision as of 13:39, 13 February 2019
Binutils 2.32
Summary
Rebase the binutils package from version 2.31 to version 2.32.
Owner
- Name: Nick Clifton [1]
- Email: nickc@redhat.com
- Release notes owner:
Current status
- Targeted release: Fedora 31
- Last updated: 2019-02-13
- Tracker bug: <will be assigned by the Wrangler>
Detailed Description
Switch the binutils package from being based on the 2.31 release of the GNU binutils to being based on the 2.32 release. This release will bring in numerous bug fixes, as well as the one new feature: The objdump program's --disassemble option can now take a parameter, specifying the starting symbol for disassembly. Disassembly will continue from this symbol up to the next symbol.
Benefit to Fedora
The main benefit will be the bug fixes and the improvement to the linker. The improvement to objdump will be of benefit to users who want to see the disassembly of just one function, rather than an entire file.
Scope
- Proposal owners:
Change the source parameter in the binutils.spec rpm and adjust the local patches to take account of the bugs that are now already fixed. This should be followed by a mass rebuild in order for the changes to be noticed across the system.
- Other developers:
No other work should be necessary. Once the rebase is in place and the buildroot contains the new binutils its use should be automatic.
- Release engineering: [2]
- List of deliverables: Just the binutils package.
- Policies and guidelines: No updates needed.
- Trademark approval: N/A (not needed for this Change)
Upgrade/compatibility impact
The binutils are backwards compatible with previous releases, so no changes should be necessary.
How To Test
The binutils package does include its own set of testsuites which check basic functionality. The real test however is by rebuilding other packages which depend upon the binutils, or more likely, upon gcc. If these packages continue to work then the binutils update has not broken anything.
User Experience
The change should not be noticeable to the user.
Dependencies
This update has no hard dependencies on any other package. There are other packages that do depend upon the binutils however. Most notably gcc and redhat-rpm-config.
Contingency Plan
- Contingency mechanism:
Revert to the 2.31 binutils as currently used in rawhide. This work can be done by me, should it prove necessary.
- Contingency deadline: Beta Freeze
- Blocks release? No
- Blocks product? None
Documentation
Documentation is not currently available, due to the fact that the 2.31 release has not yet been created. (It is hoped that the release will happen before the Fedora 29 mass rebuid on 11 July).