Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 216232 - undefined symbols in compiz plugins
Summary: undefined symbols in compiz plugins
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: compiz
Version: 6
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Kristian Høgsberg
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-11-17 21:57 UTC by Jarod Wilson
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-03-29 02:53:58 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
Undefined symbols in $libdir/compiz/lib*.so (30.63 KB, text/plain)
2006-11-17 21:57 UTC, Jarod Wilson 		no flags Details
View All

Description Jarod Wilson 2006-11-17 21:57:11 UTC 
Description of problem:
The compiz plugins are full of undefined symbols. The gl* ones can be resolved
by linking offending plugins against libGL.so. The rest... I dunno what they
should like against, looks like they may be compiz-specific symbols.

Version-Release number of selected component (if applicable):
compiz-0.0.13-0.32.20060817git.fc6.x86_64

How reproducible:
ldd -r /usr/lib64/compiz/lib*.so > /dev/null

Additional info:

The beryl packages I'm working on for Extras are similarly afflicted.
Comment 1 Jarod Wilson 2006-11-17 21:57:11 UTC 
Created attachment 141537 [details]
Undefined symbols in $libdir/compiz/lib*.so
Comment 2 Kristian Høgsberg 2007-03-29 02:53:58 UTC 
This isn't a problem.  They're plugins, not shared libraries.  The process
dlopening the .so files (compiz) is responsible for providing the unresolved
symbols, which it does by either 1) linking to libGL or other libraries to
provide the gl* symbols or 2) by exposing it's own internal API to the modules
which provides the remaining symbols.

Unresolved symbols are only a problem for shared libraries in /usr/lib that apps
actually link against.  In this case an unresolved symbol in a library will
prevent the application from running.

PS: try ldd -r on any .so file in /usr/lib/xorg :)
Comment 3 Jarod Wilson 2007-03-29 13:24:30 UTC 
Ah, okay, works for me, you definitely know better than I do. I have the
misfortune of the being the sucker that maintains the beryl bits in fedora
extras, and has someone file a similar bug report for beryl. Saw the same
w/compiz, so that's where this bug came from. I'll close the one filed against
beryl too then. Thanks! :)
Note You need to log in before you can comment on or make changes to this bug.