Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
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
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: at-spi
Version: 4.4
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Matthias Clasen
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-04-10 23:22 UTC by clee
Modified: 2012-06-20 15:56 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-20 15:56:03 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description clee 2007-04-10 23:22:18 UTC
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 15:56:03 UTC
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.