Bug 175333

Summary: modules not built correctly
Product: Red Hat Enterprise Linux 3 Reporter: Nalin Dahyabhai <nalin>
Component: gailAssignee: Matthias Clasen <mclasen>
Status: CLOSED WONTFIX QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 3.0Keywords: Desktop
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-10-19 18:50:09 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 170417, 175205    
Attachments:
Description Flags
Patch to override the tarball libtool with one which understands multilib. none

Description Nalin Dahyabhai 2005-12-08 22:49:35 UTC
Description of problem:
On x86_64, there aren't any dynamic modules (.so files) installed into
/usr/lib64/gtk-2.0/modules, only static and libtool archives (.a and .la files).

Version-Release number of selected component (if applicable):
1.2.2-1

How reproducible:
Always

Steps to Reproduce:
1. env GTK_MODULES=gail:ferret gtk-demo
  
Actual results:
"Failed to load module"

Expected results:
GTK Accessibility Module initialized
** (gtk-demo:7944): CRITICAL **: atk_relation_set_get_n_relations: assertion
`ATK_IS_RELATION_SET (set)' failed

Comment 1 Nalin Dahyabhai 2005-12-09 00:24:54 UTC
Created attachment 122048 [details]
Patch to override the tarball libtool with one which understands multilib.

Comment 4 RHEL Program Management 2007-10-19 18:50:09 UTC
This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
 
For more information of the RHEL errata support policy, please visit:
http://www.redhat.com/security/updates/errata/
 
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.