RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1271380 - chrpath missing support for 32-bit binaries
Summary: chrpath missing support for 32-bit binaries
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: chrpath
Version: 7.1
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Jeff Law
QA Contact: Martin Cermak
Vladimír Slávik
URL:
Whiteboard:
Depends On:
Blocks: 1298243 1390370
TreeView+ depends on / blocked
 
Reported: 2015-10-13 19:37 UTC by Deepu K S
Modified: 2020-09-10 09:27 UTC (History)
13 users (show)

Fixed In Version: chrpath-0.16-0.el7
Doc Type: Rebase: Bug Fixes Only
Doc Text:
_chrpath_ rebased to version 0.16 The _chrpath_ package has been upgraded to upstream version 0.16, which provides a number of bug fixes over the previous version. Notably, the *chrpath* tool could only modify the run path property of 64-bit binaries on 64-bit systems, and 32-bit binaries on 32-bit systems. This bug has been fixed, and *chrpath* on a 64-bit system can now modify run paths of binaries for a 32-bit system and binaries for a 32-bit system on a 64-bit system.
Clone Of:
Environment:
Last Closed: 2017-08-01 22:23:43 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Diff of chrpath-0.13 and chrpath-0.14 (13.21 KB, patch)
2015-10-14 08:50 UTC, Divya
no flags Details | Diff


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:2058 0 normal SHIPPED_LIVE chrpath bug fix update 2017-08-01 19:34:27 UTC

Description Deepu K S 2015-10-13 19:37:38 UTC
Description of problem:
Current `chrpath` in RHEL 7 doesn't support for 32-bit executables/libraries.

Version-Release number of selected component (if applicable):
Red Hat Enterprise Linux 7.1
chrpath-0.13-14.el7.x86_64

How reproducible:
Always

Steps to Reproduce:
1. chrpath -l <executable/library>

Actual results:
# chrpath -l program_32 
`program_32' probably isn't a 64-bit LSB-first ELF file.
elf_open: Exec format error

# chrpath -r /root/D program_32 
`program_32' probably isn't a 64-bit LSB-first ELF file.
elf_open: Exec format error

Expected results:
# chrpath -l program_32 
program_32: RPATH=/root/C/

# chrpath -r /root/D program_32 
program_32: RPATH=/root/C
program_32: new RPATH: /root/D

Additional info:
Upstream BugZilla : https://bugzilla.redhat.com/show_bug.cgi?id=1144863

Comment 1 Divya 2015-10-14 08:50:37 UTC
Created attachment 1082750 [details]
Diff of chrpath-0.13 and chrpath-0.14

Tested locally, it seems to fix the issue.

Comment 43 errata-xmlrpc 2017-08-01 22:23:43 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:2058


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