| Summary: | Missing compat-sap-c++-5.so symlink | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Marcel Kolaja <mkolaja> |
| Component: | compat-sap-c++-5 | Assignee: | Marek Polacek <mpolacek> |
| Status: | CLOSED ERRATA | QA Contact: | Michael Petlan <mpetlan> |
| Severity: | high | Docs Contact: | Lenka Špačková <lkuprova> |
| Priority: | high | ||
| Version: | 7.2 | CC: | alexander.hass, cgiunta, fdanapfe, helge.deller, kim-thomas.rehmann, mnewsome, mpetlan, mpolacek |
| Target Milestone: | rc | Keywords: | ZStream |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | compat-sap-c++-5-5.3.1-10.el7_2 | Doc Type: | Bug Fix |
| Doc Text: |
A symbolic link was previously not provided for use by SAP software. Consequently, SAP could not depend on this feature in their software for Red Hat Enterprise Linux, and hence end users could not receive SAP software versions that need this feature. With this update, the symbolic link compat-sap-c++-5.so has been added, which links to the runtime library. As a result, SAP software can use the symbolic rather than explicit library name, and hence SAP will in due course be able to release software relying upon the availability of this mechanism.
|
Story Points: | --- |
| Clone Of: | 1365181 | Environment: | |
| Last Closed: | 2016-11-09 17:18:08 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Bug Depends On: | 1365181 | ||
| Bug Blocks: | |||
|
Description
Marcel Kolaja
2016-10-06 14:32:20 UTC
$ ls -l `rpmquery -l compat-sap-c++-5` -rwxr-xr-x. 1 root root 1582128 Aug 18 11:58 /opt/rh/SAP/lib64/compat-sap-c++-5.3.1.so lrwxrwxrwx. 1 root root 23 Oct 12 12:43 /opt/rh/SAP/lib64/compat-sap-c++-5.so -> compat-sap-c++-5.3.1.so ... Checked with compat-sap-c++-5-5.3.1-10.el7_2 on x86_64 and ppc64le. Seems that these are the architectures that will be shipped. If I miss some, please tell me. Thanks. VERIFIED. But SAP HANA 2.0 / Tokyo is SAP's new release, and we have agreed that new releases and new architectures will be supported on new RHEL releases. In that case, that would be RHEL 7.3. For HANA, the request has been to support Power LE on the Tokyo release, and that will be done via RHEL 7.3. We all realize that this will require that RHEL 7.3 be certified, but it already needs to be certified to support the Power LE new architecture. We do not add new features via the EUS stream. We add new features via a new release, and are following those rules with this. If you think I am missing something on this, please let me know, but we never had plans to support the new Tokyo on the EUS release. It always needed to be moving up to the next RHEL release. Regards, Cathy (In reply to Cathy Giunta from comment #10) > But SAP HANA 2.0 / Tokyo is SAP's new release, and we have agreed that new > releases and new architectures will be supported on new RHEL releases. In > that case, that would be RHEL 7.3. > > For HANA, the request has been to support Power LE on the Tokyo release, and > that will be done via RHEL 7.3. > > We all realize that this will require that RHEL 7.3 be certified, but it > already needs to be certified to support the Power LE new architecture. > > We do not add new features via the EUS stream. We add new features via a new > release, and are following those rules with this. > > If you think I am missing something on this, please let me know, but we > never had plans to support the new Tokyo on the EUS release. It always > needed to be moving up to the next RHEL release. Cathy, I can confirm that we need this symlink for RHEL 7.2. Please let us not start the whole discussion again. Thank you, Alexander. (In reply to Cathy Giunta from comment #10) > But SAP HANA 2.0 / Tokyo is SAP's new release, and we have agreed that new > releases and new architectures will be supported on new RHEL releases. In > that case, that would be RHEL 7.3. > > For HANA, the request has been to support Power LE on the Tokyo release, and > that will be done via RHEL 7.3. > > We all realize that this will require that RHEL 7.3 be certified, but it > already needs to be certified to support the Power LE new architecture. > > We do not add new features via the EUS stream. We add new features via a new > release, and are following those rules with this. This bug is not for adding new features but to provide a fix to an already existing feature. > If you think I am missing something on this, please let me know, but we > never had plans to support the new Tokyo on the EUS release. It always > needed to be moving up to the next RHEL release. > > Regards, > Cathy Thanks for the clarification on this. 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://rhn.redhat.com/errata/RHBA-2016-2690.html |