Bug 11550 – libstdc++ doesn't have compatibility library for x86; let me upgrade and break groff?

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 11550 - libstdc++ doesn't have compatibility library for x86; let me upgrade and break groff?

Summary:	libstdc++ doesn't have compatibility library for x86; let me upgrade and brea...

Status:	CLOSED RAWHIDE

Aliases:	None

Product:	Red Hat Raw Hide
Classification:	Retired
Component:	libstdc++ (Show other bugs)
Sub Component:
Version:	1.0
Hardware:	All Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Jakub Jelinek
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2000-05-21 11:39 EDT by Jonathan Kamens
Modified:	2008-05-01 11:37 EDT (History)
CC List:	1 user (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2000-05-22 10:53:07 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)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Jonathan Kamens 2000-05-21 11:39:18 EDT

I installed libstdc++-2.95.3-0.20000517.  It doesn't include the
backward-compatibility library libstdc++-libc6.1-2.so.3 for x86, although
there's code in the spec file which seems to try to install it (at least
for sparc).  It should be included for x86 too.

I was able to install this upgrade even though groff-1.15-9 requires
libstdc++-libc6.1-2.so.3.  I do not understand why I was allowed to install
this upgrade; shouldn't rpm have informed me that the upgrade would erase a
library which another installed package depends upon?

Comment 1 Cristian Gafton 2000-05-22 10:53:59 EDT

assign to jakub

Comment 2 Jakub Jelinek 2000-09-05 04:42:20 EDT

This has been fixed since then, there are compat-libstdc++ and libstdc++
as separated packages

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