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.
The ifunc support for the AArch64 architecture is still currently experimental.
Hence this test, and others, are not yet working. I have added a patch to skip
the ifunc execute tests for the AArch64.
The ifunc support for the AArch64 architecture is still currently experimental.
Hence this test, and others, are not yet working. I have added a patch to skip
the ifunc execute tests for the AArch64, which will fix this particular BZ for now.
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:1864
Description of problem: aarch64-redhat-linux-gcc -B/root/rpmbuild/BUILD/binutils-2.27/ld/tmpdir/ld/ -I/root/rpmbuild/BUILD/binutils-2.27/ld/testsuite/ld-ifunc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -c -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -c /root/rpmbuild/BUILD/binutils-2.27/ld/testsuite/ld-ifunc/dummy.c -o tmpdir/dummy.o Executing on host: sh -c {aarch64-redhat-linux-gcc -B/root/rpmbuild/BUILD/binutils-2.27/ld/tmpdir/ld/ -I/root/rpmbuild/BUILD/binutils-2.27/ld/testsuite/ld-ifunc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -c -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -c /root/rpmbuild/BUILD/binutils-2.27/ld/testsuite/ld-ifunc/dummy.c -o tmpdir/dummy.o 2>&1} /dev/null ld.tmp (timeout = 300) spawn [open ...] /root/rpmbuild/BUILD/binutils-2.27/ld/ld-new -m aarch64linux -o tmpdir/pr18841b -dynamic-linker /lib/ld-linux-aarch64.so.1 /usr/lib/gcc/aarch64-redhat-linux/4.8.5/../../../../lib64/crt1.o /usr/lib/gcc/aarch64-redhat-linux/4.8.5/../../../../lib64/crti.o /usr/lib/gcc/aarch64-redhat-linux/4.8.5/crtbegin.o -L/root/rpmbuild/BUILD/binutils-2.27/ld/testsuite/ld-ifunc tmpdir/pr18841a.o tmpdir/libpr18841b.so tmpdir/dummy.o -ldl -ldl -L/usr/lib/gcc/aarch64-redhat-linux/4.8.5/../../../../lib64 --start-group /usr/lib/gcc/aarch64-redhat-linux/4.8.5/libgcc.a /usr/lib/gcc/aarch64-redhat-linux/4.8.5/libgcc_eh.a -lc --end-group /usr/lib/gcc/aarch64-redhat-linux/4.8.5/crtend.o /usr/lib/gcc/aarch64-redhat-linux/4.8.5/../../../../lib64/crtn.o Executing on host: sh -c {/root/rpmbuild/BUILD/binutils-2.27/ld/ld-new -m aarch64linux -o tmpdir/pr18841b -dynamic-linker /lib/ld-linux-aarch64.so.1 /usr/lib/gcc/aarch64-redhat-linux/4.8.5/../../../../lib64/crt1.o /usr/lib/gcc/aarch64-redhat-linux/4.8.5/../../../../lib64/crti.o /usr/lib/gcc/aarch64-redhat-linux/4.8.5/crtbegin.o -L/root/rpmbuild/BUILD/binutils-2.27/ld/testsuite/ld-ifunc tmpdir/pr18841a.o tmpdir/libpr18841b.so tmpdir/dummy.o -ldl -ldl -L/usr/lib/gcc/aarch64-redhat-linux/4.8.5/../../../../lib64 --start-group /usr/lib/gcc/aarch64-redhat-linux/4.8.5/libgcc.a /usr/lib/gcc/aarch64-redhat-linux/4.8.5/libgcc_eh.a -lc --end-group /usr/lib/gcc/aarch64-redhat-linux/4.8.5/crtend.o /usr/lib/gcc/aarch64-redhat-linux/4.8.5/../../../../lib64/crtn.o 2>&1} /dev/null ld.tmp (timeout = 300) spawn [open ...] Running: tmpdir/pr18841b > tmpdir/pr18841b.out child killed: SIGABRT FAIL: Run pr18841 with libpr18841b.so Version-Release number of selected component (if applicable): binutils-2.27-2.base.el7.aarch64 gcc-4.8.5-11.el7.aarch64 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: