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.
Description of problem:
cpio: gcc-4.4.5-20110214/obj-x86_64-redhat-linux/x86_64-redhat-linux/gnu/java/locale/LocaleData.java: Cannot stat: No such file or directory
cpio: gcc-4.4.5-20110214/obj-x86_64-redhat-linux/x86_64-redhat-linux/gnu/java/security/Configuration.java: Cannot stat: No such file or directory
cpio: gcc-4.4.5-20110214/obj-x86_64-redhat-linux/x86_64-redhat-linux/libjava/<stdin>: Cannot stat: No such file or directory
cpio: libjava/libltdl/ltdl.c: Cannot stat: No such file or directory
cpio: libjava/libltdl/ltdl.h: Cannot stat: No such file or directory
254660 blocks
+ /usr/lib/rpm/check-rpaths /usr/lib/rpm/check-buildroot
*******************************************************************************
*
* WARNING: 'check-rpaths' detected a broken RPATH and will cause 'rpmbuild'
* to fail. To ignore these errors, you can set the '$QA_RPATHS'
* environment variable which is a bitmask allowing the values
* below. The current value of QA_RPATHS is 0x0000.
*
* 0x0001 ... standard RPATHs (e.g. /usr/lib); such RPATHs are a minor
* issue but are introducing redundant searchpaths without
* providing a benefit. They can also cause errors in multilib
* environments.
* 0x0002 ... invalid RPATHs; these are RPATHs which are neither absolute
* nor relative filenames and can therefore be a SECURITY risk
* 0x0004 ... insecure RPATHs; these are relative RPATHs which are a
* SECURITY risk
* 0x0008 ... the special '$ORIGIN' RPATHs are appearing after other
* RPATHs; this is just a minor issue but usually unwanted
* 0x0010 ... the RPATH is empty; there is no reason for such RPATHs
* and they cause unneeded work while loading libraries
* 0x0020 ... an RPATH references '..' of an absolute path; this will break
* the functionality when the path before '..' is a symlink
*
*
* Examples:
* - to ignore standard and empty RPATHs, execute 'rpmbuild' like
* $ QA_RPATHS=$[ 0x0001|0x0010 ] rpmbuild my-package.src.rpm
* - to check existing files, set $RPM_BUILD_ROOT and execute check-rpaths like
* $ RPM_BUILD_ROOT=<top-dir> /usr/lib/rpm/check-rpaths
*
*******************************************************************************
ERROR 0020: file '/usr/lib64/gcj-4.4.4/libjawt.so' contains an rpath referencing '..' of an absolute path [/usr/lib/../lib64/gcj-4.4.5]
error: Bad exit status from /var/tmp/rpm-tmp.AYlhVS (%install)
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
1) check-rpath at least from what I can see is not enabled by default, you must have tweaked your rpm configuration.
2) there is nothing wrong on the RPATH
I'd not call it tweaking,
barely a few custom paths into evn
%_builddir %{_topdir}/BUILD/%_host_vendor/%{dist}
%_buildrootdir %{_topdir}/BUILDROOT/%_host_vendor/%{dist}
%_srcrpmdir %{_topdir}/SRPMS/%_host_vendor/%{dist}
%_rpmdir %{_topdir}/RPMS/%_host_vendor/%{dist}
%_specdir %{_topdir}/SPECS/%_host_vendor/%{dist}
plus -mtune=native
check-rpaths returns 0
how could these break rebuild?