Bug 235950 – libspi.so does not link against all of the libraries it should

Bug 235950 - libspi.so does not link against all of the libraries it should

Summary:	libspi.so does not link against all of the libraries it should

Status:	CLOSED WONTFIX

Aliases:	None

Product:	Red Hat Enterprise Linux 4
Classification:	Red Hat
Component:	at-spi (Show other bugs)
Sub Component:
Version:	4.4
Hardware:	x86_64 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Matthias Clasen
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2007-04-10 19:22 EDT by clee
Modified:	2012-06-20 11:56 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:	2012-06-20 11:56:03 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 clee 2007-04-10 19:22:18 EDT

Description of problem:
There are unresolved symbols in libspi.so as shipped in RHEL4U4.

Version-Release number of selected component (if applicable):
at-spi-devel-1.6.0-3

How reproducible:
Always

Steps to Reproduce:
1. ldd -u /usr/lib64/libspi.so
2. Look at all the symbol lookup errors
3. Weep
  
Actual results:
Tears of unfathomable sadness

Expected results:
Joy everlasting

Additional info:
This is dirty like zebra. There are 92 other libraries in /usr/lib64 on RHEL4U4
that also have unresolved symbols.

Comment 1 Jiri Pallich 2012-06-20 11:56:03 EDT

Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. 
Please See https://access.redhat.com/support/policy/updates/errata/

If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.

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