Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 2189453

Summary: Provide a compat-sap-c++ package without a version string as part of the package name
Product: Red Hat Enterprise Linux 8 Reporter: Bernd Finger <bfinger>
Component: compat-sap-c++-10Assignee: Patrick Palka <ppalka>
Status: CLOSED MIGRATED QA Contact: qe-baseos-tools-bugs
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 8.9CC: abezhani, cbrune, fweimer, ppalka, sipoyare
Target Milestone: rcKeywords: FutureFeature, MigratedToJIRA, Triaged
Target Release: ---Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-09-22 15:15:57 UTC Type: Story
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: 2232169    
Bug Blocks: 2143913, 2191716    

Description Bernd Finger 2023-04-25 10:04:00 UTC
The compat-sap-c++ packages provide forward compatibility on RHEL versions which have been built with previous GCC versions. So SAP software which have been built with more recent GCC versions can be used on older RHEL versions. Example: RHEL 8 is based on GCC 8 and SAP HANA SPS06 has been built with GCC 10. So a library which contains the GCC 10 symbols is required in this case. This library is currently contained in a package named compat-sap-c++-10.

We should replace the compat-sap-c++-* packages by a compat-sap-c++ package without a version string in its package name. This package will also contain a file/link named /opt/rh/SAP/lib64/libstdc++.so.6 pointing to the library which contains the latest GCC symbols so that future versions of SAP software can access the symbols by RUNPATH, RPATH, or LD_LIBRARY_PATH without having to create a new link in a different directory.

Why?
- It will be easier to document and explain which package(s) must be installed for SAP software
- The installation of SAP software will be simplified

Version-Release number of selected component (if applicable):

Additional info:
We must ensure that all possible and supported combinations of SAP HANA and SAP NetWeaver/SAP ABAP Application Platform can be installed on a single RHEL system.

Comment 2 RHEL Program Management 2023-09-22 15:15:08 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 3 RHEL Program Management 2023-09-22 15:15:57 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.