Bug 1660558
| Summary: | Unresolvable `R_X86_64_NONE` relocation [rhel-7.5.z] | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | RAD team bot copy to z-stream <autobot-eus-copy> |
| Component: | binutils | Assignee: | Nick Clifton <nickc> |
| Status: | CLOSED ERRATA | QA Contact: | Miloš Prchlík <mprchlik> |
| Severity: | low | Docs Contact: | |
| Priority: | high | ||
| Version: | 7.6 | CC: | fweimer, law, mprchlik, ohudlick, vmukhame |
| Target Milestone: | rc | Keywords: | ZStream |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | https://stackoverflow.com/questions/48706962/unresolvable-r-x86-64-none-relocation | ||
| Whiteboard: | |||
| Fixed In Version: | binutils-2.27-28.base.el7_5.2 | Doc Type: | Bug Fix |
| Doc Text: |
`strip` no longer malforms binary files built with tools that use a later *BFD* library version
Previously, the `strip` tool created an invalid binary file if the file was originally produced by tools that use a later version of the *BFD* library than `strip`. As a consequence running the resulting binary file failed and generated an error message about an unresolvable relocation. *BFD* has been modified to report situations where it cannot recognize its future features instead of damaging the code that contains these features. As a result, `strip` now generates an error message and aborts in this situation.
|
Story Points: | --- |
| Clone Of: | 1553842 | Environment: | |
| Last Closed: | 2019-01-29 16:07:17 UTC | Type: | --- |
| 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: | 1553842 | ||
| Bug Blocks: | |||
|
Description
RAD team bot copy to z-stream
2018-12-18 15:43:57 UTC
Fixed in binutils-2.27-28.base.el7_5.2. Verified using the upstream test case. 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-2019:0203 |