2023-12-12 18:20:55 + /usr/lib/rpm/check-rpaths
2023-12-12 18:20:55 *******************************************************************************
2023-12-12 18:20:55 *
2023-12-12 18:20:55 * WARNING: 'check-rpaths' detected a broken RPATH OR RUNPATH and will cause
2023-12-12 18:20:55 *          'rpmbuild' to fail. To ignore these errors, you can set the
2023-12-12 18:20:55 *          '$QA_RPATHS' environment variable which is a bitmask allowing the
2023-12-12 18:20:55 *          values below. The current value of QA_RPATHS is 0x0000.
2023-12-12 18:20:55 *
2023-12-12 18:20:55 *    0x0001 ... standard RPATHs (e.g. /usr/lib); such RPATHs are a minor
2023-12-12 18:20:55 *               issue but are introducing redundant searchpaths without
2023-12-12 18:20:55 *               providing a benefit. They can also cause errors in multilib
2023-12-12 18:20:55 *               environments.
2023-12-12 18:20:55 *    0x0002 ... invalid RPATHs; these are RPATHs which are neither absolute
2023-12-12 18:20:55 *               nor relative filenames and can therefore be a SECURITY risk
2023-12-12 18:20:55 *    0x0004 ... insecure RPATHs; these are relative RPATHs which are a
2023-12-12 18:20:55 *               SECURITY risk
2023-12-12 18:20:55 *    0x0008 ... the special '$ORIGIN' RPATHs are appearing after other
2023-12-12 18:20:55 *               RPATHs; this is just a minor issue but usually unwanted
2023-12-12 18:20:55 *    0x0010 ... the RPATH is empty; there is no reason for such RPATHs
2023-12-12 18:20:55 *               and they cause unneeded work while loading libraries
2023-12-12 18:20:55 *    0x0020 ... an RPATH references '..' of an absolute path; this will break
2023-12-12 18:20:55 *               the functionality when the path before '..' is a symlink
2023-12-12 18:20:55 *          
2023-12-12 18:20:55 *
2023-12-12 18:20:55 * Examples:
2023-12-12 18:20:55 * - to ignore standard and empty RPATHs, execute 'rpmbuild' like
2023-12-12 18:20:55 *   $ QA_RPATHS=$(( 0x0001|0x0010 )) rpmbuild my-package.src.rpm
2023-12-12 18:20:55 * - to check existing files, set $RPM_BUILD_ROOT and execute check-rpaths like
2023-12-12 18:20:55 *   $ RPM_BUILD_ROOT=<top-dir> /usr/lib/rpm/check-rpaths
2023-12-12 18:20:55 *  
2023-12-12 18:20:55 *******************************************************************************
2023-12-12 18:20:55 ERROR   0020: file '/opt/openEuler/gcc-toolset-7/root/usr/lib64/libtsan.so.0.0.0' contains an  referencing '..' of an absolute path [/opt/openEuler/gcc-toolset-7/root/usr/lib/../lib64]
2023-12-12 18:20:56 ERROR   0020: file '/opt/openEuler/gcc-toolset-7/root/usr/lib64/libubsan.so.0.0.0' contains an  referencing '..' of an absolute path [/opt/openEuler/gcc-toolset-7/root/usr/lib/../lib64]
2023-12-12 18:20:56 ERROR   0020: file '/opt/openEuler/gcc-toolset-7/root/usr/lib64/libasan.so.4.0.0' contains an  referencing '..' of an absolute path [/opt/openEuler/gcc-toolset-7/root/usr/lib/../lib64]
2023-12-12 18:20:56 ERROR   0020: file '/opt/openEuler/gcc-toolset-7/root/usr/lib64/liblsan.so.0.0.0' contains an  referencing '..' of an absolute path [/opt/openEuler/gcc-toolset-7/root/usr/lib/../lib64]
2023-12-12 18:21:00 
2023-12-12 18:21:00 
2023-12-12 18:21:00 RPM build errors:
2023-12-12 18:21:00 error: Bad exit status from /var/tmp/rpm-tmp.336Nmw (%install)
2023-12-12 18:21:00     Macro expanded in comment on line 2412: %{_prefix}/lib/gcc/%{gcc_target_platform}/%{gcc_major}/include/itm.h
2023-12-12 18:21:00 
2023-12-12 18:21:00     Macro expanded in comment on line 2413: %{_prefix}/lib/gcc/%{gcc_target_platform}/%{gcc_major}/include/itm_weak.h
2023-12-12 18:21:00 
2023-12-12 18:21:00     bad date in %changelog: Thu June 08 2023 zhangwuji1995 <zhangwuji1@huawei.com> 7.3.0-1
2023-12-12 18:21:00     Bad exit status from /var/tmp/rpm-tmp.336Nmw (%install)