Bug 72677 - libstdc++.so.4 missing
libstdc++.so.4 missing
Status: CLOSED WONTFIX
Product: Red Hat Raw Hide
Classification: Retired
Component: compat-gcc (Show other bugs)
1.0
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jakub Jelinek
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2002-08-26 11:57 EDT by Moritz Barsnick
Modified: 2008-05-01 11:38 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2002-08-26 11:57:27 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Moritz Barsnick 2002-08-26 11:57:20 EDT
Description of Problem:

Version 3.1 of the gcc/g++/libstdc++ suite provided a libstdc++
with the soname/filename libstdc++.so.4. g++-3.2 has an
incompatible API and therefore correctly (IMHO) delivers
libstdc++.so.5.

Yet there are still some apps from the Beta (IIRC) around (and
from other distributions using g++-3.1) requiring libstdc++.so.4,
but this file is not found in the usual place "compat-libstdc++"
(or anywhere else for that matter) yet.

Version-Release number of selected component (if applicable):
compat-libstdc++-7.3-2.96.110

How Reproducible:
Always

Steps to Reproduce:
1. Run a program which was dynamically linked against
   libstdc++.so.4.
2. 
3. 

Actual Results:
libstdc++.so.4 is missing, program doesn't run.

Expected Results:
Program should run.

Additional Information:
	
Alas. I can install the packages libstdc++-3.1-xy and libstdc++-3.2.zz
in parallel (-ivh instead of -Uvh), there are no conflicts. But IMHO
it's "not the way to go" [tm].  ;-)  And libstdc++-3.1-xy isn't
being delivered anymore.

A fix would make RedHat just that little bit more compatible to
many apps.  :)

Thanks for listening,
Moritz
Comment 1 Jakub Jelinek 2002-08-26 12:02:21 EDT
We are shipping compat libraries only for the compilers we have shipped.
Shipping further libraries means we'd have to support them. The amount
of apps linked against 3.1 libstdc++ is still small and they'll be eventually
recompiled with 3.2 anyway.
There is nothing that prevents downloading packaged 3.1 libstdc++ from the
same place you downloaded those apps linked against it or build it yourself.

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