Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 1285614

Summary: ckermit FTBFS on aarch64 epel7
Product: Red Hat Enterprise Linux 7 Reporter: Yaakov Selkowitz <yselkowi>
Component: binutilsAssignee: Nick Clifton <nickc>
Status: CLOSED ERRATA QA Contact: Miloš Prchlík <mprchlik>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.2CC: jfeeney, law, mcermak, mnewsome, mprchlik, nickc, ohudlick
Target Milestone: rcKeywords: Patch
Target Release: ---   
Hardware: aarch64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Cause: A bug in the linker meant that it was unable to link some AArch64 binaries. Consequence: Some AArch64 programs could not be linked. Fix: Rebase the binutils to the 2.25.1 release which includes a fix for this problem. Result: No more problems linking AArch64 binaries.
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-04 01:53:47 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: 1277314, 1285484, 1297579, 1313485    

Description Yaakov Selkowitz 2015-11-26 04:20:38 UTC
Attempting to build ckermit from Fedora EPEL on RHELSA 7.2 ends with the following error:

http://download.eng.bos.redhat.com/brewroot/work/tasks/411/10150411/build.log

ckcpro.o: In function `wart':
/builddir/build/BUILD/ckermit-9.0.302/ckcpro.c:1510:(.text+0x3080): relocation truncated to fit: R_AARCH64_LDST64_ABS_LO12_NC against symbol `dest' defined in .bss section in ckcmai.o
collect2: error: ld returned 1 exit status

Note that this package builds correctly on F23, but not F22 or earlier either (with the same error).  Apparently there is a fix in more recent toolchain that we are missing in 7.2.

Comment 2 Nick Clifton 2016-01-29 11:30:48 UTC
The new 7.3 binutils is based upon the F23 binutils, so changing this BZ to MODIFIED so that QE can test/verify.

Comment 5 Miloš Prchlík 2016-06-27 12:14:36 UTC
Verified for build binutils-2.25.1-20.base.el7 - ld refuses to link the binary - which the expected behavior, as per https://bugzilla.redhat.com/show_bug.cgi?id=1300543#c3 - but provides more descriptive message.

Comment 9 errata-xmlrpc 2016-11-04 01:53:47 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://rhn.redhat.com/errata/RHBA-2016-2265.html