| Summary: | Rebase elfutils to 0.168 | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | mbenitez |
| Component: | elfutils | Assignee: | Mark Wielaard <mjw> |
| Status: | CLOSED ERRATA | QA Contact: | Martin Cermak <mcermak> |
| Severity: | unspecified | Docs Contact: | Vladimír Slávik <vslavik> |
| Priority: | unspecified | ||
| Version: | 7.4 | CC: | bgollahe, mcermak, mjw, mnewsome, vslavik |
| Target Milestone: | rc | Keywords: | Rebase |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | elfutils-0.168-5.el7 | Doc Type: | Rebase: Bug Fixes and Enhancements |
| Doc Text: |
_elfutils_ rebased to version 0.168
The _elfutils_ package has been upgraded to upstream version 0.168, which provides a number of bug fixes and enhancements:
* The option `--symbols` of the *eu-readelf* utility now allows selecting the section for displaying symbols.
* New functions for the creation of ELF/DWARF string tables have been added to the *libdw* library.
* The `DW_LANG_PL1` constant has been changed to `DW_LANG_PLI`. The previous name is still accepted.
* The return type of the `gelf_newehdr` and `gelf_newphdr` functions from the *libelf* library has been changed to `void*` for source compatibility with other *libelf* implementations. This change retains binary compatibility on all platforms supported by Red Hat Enterprise Linux.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-08-01 22:06:37 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: | |
| Bug Depends On: | |||
| Bug Blocks: | Red Hat1390370, Red Hat1411714 | ||
|
Description
mbenitez
2016-11-30 20:44:30 UTC
0.168 was released, it is mostly a minor bug fix release compared to 0.167. 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/RHEA-2017:2020 |