Bug 1779597
Summary: | After installation of gcc-c++ broken symlinks under /usr/lib/gcc/x86_64-redhat-linux/8/32 | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | Michele Casaburo <mcasabur> |
Component: | gcc | Assignee: | Marek Polacek <mpolacek> |
gcc sub component: | system-version | QA Contact: | Alexandra Petlanová Hájková <ahajkova> |
Status: | CLOSED ERRATA | Docs Contact: | |
Severity: | medium | ||
Priority: | unspecified | CC: | ahajkova, fweimer, jakub, mcermak, ohudlick, sipoyare, swachira, vmukhame |
Version: | 8.1 | Keywords: | Bugfix, Triaged |
Target Milestone: | rc | ||
Target Release: | 8.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | gcc-8.4.1-1.el8 | Doc Type: | No Doc Update |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2021-05-18 13:28:00 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: | 1894575 |
Description
Michele Casaburo
2019-12-04 10:43:04 UTC
This is completely intentional, the gcc.x86_64 etc. packages must not force installation of *.i686 packages, and the symlinks will be satisfied if the corresponding *.i686 packages are installed, if not, the compiler will simply support -m64 only or -m32 only for compilation that doesn't need those. For libasan.a, you can install libasan-static.i686, for libitm.a libitm-static.i686, for libquadmath.a libquadmath-static.i686, for libubsan.a libubsan-static.i686. With weak and rich dependencies we could perhaps improve the situation somewhat, e.g. recommend installation of the i686 packages if glibc-devel.i686 or glibc.i686 is installed. Recommends: instead of Requires: means that the user can remove the packages again, and they will only get them if there are already some 32-bit multilibs. It looks like something that could we try in Fedora. (In reply to Jakub Jelinek from comment #1) > This is completely intentional, the gcc.x86_64 etc. packages must not force > installation of *.i686 packages, and the symlinks will be satisfied if the > corresponding *.i686 packages are installed, if not, the compiler will > simply support -m64 only or -m32 only for compilation that doesn't need > those. I understand, and I definitely agree that forcing i686 packages installation would be a bad idea. Just my 2c here, as I might miss apiece, but wouldn't be cleaner if the symlinks were created upon installation of the relevant i686 packages ? My customer, who is indeed building 32bits applications, noticing the broken links did not have a good impression. > For libasan.a, you can install libasan-static.i686, for libitm.a > libitm-static.i686, for libquadmath.a libquadmath-static.i686, for > libubsan.a libubsan-static.i686. I had a quick check again, but I could not find those packages in any RHEL8 related repository. These are available for RHEL7 libasan-static.i686 libitm-static.i686 libquadmath-static.i686 while I could not find libubsan-static.i686 anywhere > wouldn't be cleaner if the symlinks were created upon installation of the relevant i686 packages ?
Can we get a response on this?
Some i686 packages are missing from RHEL 8 repositories for which there are still broken links. Should this not be addressed?
libubsan-static is provided via devtoolset-9-libubsan-devel on RHEL 7. We build libasan-static.i686 libitm-static.i686 libquadmath-static.i686 libubsan-static.i686 for RHEL 8 too, they just are not available in BaseOS or AppStream or CRB for some reason. Thanks Marek. I have raised a request for these packages to be added to RHEL 8 repos. 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 (gcc bug fix and enhancement update), 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-2021:1571 |