Bug 101743 - LTC3825-libstdc++-libc6.2-2.so.3 missing from install images
LTC3825-libstdc++-libc6.2-2.so.3 missing from install images
Status: CLOSED CURRENTRELEASE
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: distribution (Show other bugs)
3.0
s390 Linux
high Severity high
: ---
: ---
Assigned To: Bill Nottingham
Mike McLean
:
: 102314 (view as bug list)
Depends On:
Blocks: 97942
  Show dependency treegraph
 
Reported: 2003-08-06 10:48 EDT by Bob Johnson
Modified: 2014-03-16 22:37 EDT (History)
3 users (show)

See Also:
Fixed In Version: RHEL3 U6
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-10-07 16:41:44 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Greg Kelleher 2003-08-06 10:48:48 EDT
The following has be reported by IBM LTC:  
libstdc++-libc6.2-2.so.3 missing from install images
Hardware Environment:
System 390

Software Environment:
RHEL 3 beta 1

Steps to Reproduce:
1. Install RHEL 3 beta 1
2. Look for compatibility libraries to install libstdc++-libc6.2-2.so.3

Actual Results:
There are no images on the CD's that contain libstdc++-libc6.2-2.so.3.  This
compatibility library is necessary for several already shipped IBM products. For
example, db2 depends on this library.  This library is contained on the x86 
install.

Expected Results:
Should be able to install library.

Additional Information:Glen / Greg,
Please report RHEL beta problem to RedHat.
NOTE : severity is blocking.  Thanks
Comment 4 Karen Bennet 2003-08-27 01:10:13 EDT
*** Bug 102314 has been marked as a duplicate of this bug. ***
Comment 8 Florian La Roche 2003-09-17 03:56:06 EDT
Compat rpms and a current kernel for java testing are on
http://people.redhat.com/laroche/.not/

greetings,

Florian La Roche
Comment 9 Bill Nottingham 2005-10-07 16:41:44 EDT
Closing this out.

Note You need to log in before you can comment on or make changes to this bug.