Bug 1433946
| Summary: | Deriving libasan package from Dev Tools/ Software Collection main paradigm | ||
|---|---|---|---|
| Product: | Red Hat Developer Toolset | Reporter: | Dmitry Zhukovski <dzhukous> |
| Component: | doc-Release_Notes | Assignee: | Lenka Špačková <lkuprova> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | unspecified | CC: | jhradile, kanderso, law, lkocman, mcermak, mnewsome, mpolacek |
| Target Milestone: | alpha | Keywords: | Reopened |
| Target Release: | 6.1 | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Known Issue | |
| Doc Text: |
GCC in Red Hat Developer Toolset 3.x contained the libasan package, which might have conflicted with the system version of libasan. As a consequence, depending on which libasan was present in the system, the -fsanitize=address tool worked only either with the system GCC or with the Red Hat Developer Toolset version of GCC, but not with both at the same time. To prevent the described conflict, in Red Hat Developer Toolset 4.x and later versions, the package was renamed to libasanN, where N is a number. However, if the Red Hat Software Collections repository is enabled, the problem can occur after the system update because the system version of libasan is provided in an earlier version than the Red Hat Developer Toolset 3.x version, which is still available in the repository. To work around this problem, exclude this package while updating:
~]$ yum update --exclude=libasan
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-04-26 10:59:33 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: | |||
|
Description
Dmitry Zhukovski
2017-03-20 12:42:18 UTC
Please note that support for Red Hat Developer Toolset 3.x ended with the release of Red Hat Developer Toolset 6.0: https://access.redhat.com/support/policy/updates/rhscl That said, this was a known issue with Red Hat Developer Toolset 3.x libasan, which was addressed in Red Hat Developer Toolset 4.0 and later. The libasan package in Red Hat Developer Toolset was renamed "libasan2", which does not conflict with the equivalent earlier package in Red Hat Enterprise Linux 7. Yes - indeed - DTS 4 and DTS6 do not have that dependencies and works like charm not interfere with system libs/tools. However - simple "yum update" with enabled SCL repo breaks everything as it tries to install "broken" libasan-4.9.2-6.2.el7. After that update user can't use system gcc/libs anymore. Can we something here ? I guess simple minor-minor update of the package that does ADD it's libs instead of REPLACING.. ? br, dmitry ----------------------------------------------------------- [root@rhel7-1 ~]# yum update Loaded plugins: package_upload, product-id, search-disabled-repos, subscription-manager Resolving Dependencies --> Running transaction check ---> Package libasan.x86_64 0:4.8.5-11.el7 will be updated ---> Package libasan.x86_64 0:4.9.2-6.2.el7 will be an update --> Finished Dependency Resolution Dependencies Resolved ======================================================================================================================== Package Arch Version Repository Size ======================================================================================================================== Updating: libasan x86_64 4.9.2-6.2.el7 rhel-server-rhscl-7-rpms 215 k Transaction Summary ======================================================================================================================== Upgrade 1 Package Total download size: 215 k Is this ok [y/d/N]: y Downloading packages: Delta RPMs disabled because /usr/bin/applydeltarpm not installed. libasan-4.9.2-6.2.el7.x86_64.rpm | 215 kB 00:00:01 Running transaction check Running transaction test Transaction test succeeded Running transaction Updating : libasan-4.9.2-6.2.el7.x86_64 1/2 Cleanup : libasan-4.8.5-11.el7.x86_64 2/2 Uploading Package Profile Verifying : libasan-4.9.2-6.2.el7.x86_64 1/2 Verifying : libasan-4.8.5-11.el7.x86_64 2/2 Updated: libasan.x86_64 0:4.9.2-6.2.el7 Complete! Since support for Red Hat Developer Toolset 3.x ended, we can hardly change anything. As a workaround, I think you can use # yum update --exclude=libasan I might be wrong but I think it's bad attitude to tell customer - go and fix yourself your scripts/config files to exclude some package that we still ship as part of SCL repository and that does break system's libasan even if they do not install DTS-3. Matt - what is our conclusion on that ? |