Red Hat Bugzilla – Bug 1465510
gcc and gcc-libraries debuginfo clash on aarch64
Last modified: 2018-04-10 11:11:26 EDT
Currently, gcc-4.8.5-16.el7 for aarch64 doesn't ship libatomic, so gcc-libraries on aarch64 comes with libatomic, to support DTS-built applications. Upstream 4.8 doesn't support libatomic on aarch64: in libatomic/configure.tgt you'll find case "${target}" in aarch64*) # This is currently not supported in AArch64. UNSUPPORTED=1 ;; But redhat/gcc-4.8 actually supports libatomic on aarch64; the bits above were removed in <https://gcc.gnu.org/viewcvs/gcc/branches/redhat/gcc-4_8-branch/libatomic/configure.tgt?r1=195337&r2=212553>. But the spec file for rhel7 gcc has: %ifarch %{ix86} x86_64 ppc ppc64 ppc64le ppc64p7 s390 s390x %{arm} %global build_libatomic 1 %else %global build_libatomic 0 %if %{build_libatomic} %files -n libatomic [...] which means that we *build* libatomic on aarch64, it just isn't included in a subpackage. But it still ends up in the debuginfo! So gcc-debuginfo and gcc-libraries-debuginfo clash. I believe we should: * fix rhel7 gcc spec file so it actually includes the libatomic subpackage on aarch64, * drop the libatomic subpackage from gcc-libraries.
So the debuginfos don't clash anymore: # rpmquery -a | grep gcc | grep debuginfo gcc-debuginfo-4.8.5-26.el7.aarch64 gcc-base-debuginfo-4.8.5-26.el7.aarch64 gcc-libraries-debuginfo-7.2.1-1.1.1.el7.aarch64 I don't know what exactly changed, but libatomic remains a part of gcc-libraries, its debuginfo is in gcc-libraries-debuginfo, gcc-debuginfo no more contains conflicting files. So it makes sense and works for me. VERIFIED.
(In reply to Michael Petlan from comment #7) > So the debuginfos don't clash anymore: > > # rpmquery -a | grep gcc | grep debuginfo > gcc-debuginfo-4.8.5-26.el7.aarch64 > gcc-base-debuginfo-4.8.5-26.el7.aarch64 > gcc-libraries-debuginfo-7.2.1-1.1.1.el7.aarch64 > > I don't know what exactly changed, but libatomic remains a part of > gcc-libraries, its debuginfo is in gcc-libraries-debuginfo, gcc-debuginfo no > more contains conflicting files. So it makes sense and works for me. Correct, the change was in the end in gcc, so this is expected.
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/RHSA-2018:0849