| Summary: | Xdmx shouldn't depend on xaw7 - xaw8 does the same thing | ||||||
|---|---|---|---|---|---|---|---|
| Product: | xorg | Reporter: | Bernhard Rosenkraenzer <bero> | ||||
| Component: | Build/Modular | Assignee: | Xorg Project Team <xorg-team> | ||||
| Status: | RESOLVED WONTFIX | QA Contact: | Xorg Project Team <xorg-team> | ||||
| Severity: | normal | ||||||
| Priority: | high | Keywords: | patch | ||||
| Version: | 7.0.0 | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| i915 platform: | i915 features: | ||||||
| Attachments: |
|
||||||
|
Description
Bernhard Rosenkraenzer
2006-01-25 01:44:43 UTC
Created attachment 4456 [details] [review] Patch that checks for both xaw8 and xaw7 A better fix would be providing a generic xaw.pc in libXaw and then use a dependency on xaw >= 7.0 i find it humorous that xaw is considered for inclusion in a "no legacy" system in the first place. It's a necessary evil as long as openoffice.org keeps linking to it (In reply to comment #4) > It's a necessary evil as long as openoffice.org keeps linking to it So, quick check of that against an FC5 box. The only file in /usr/lib/openoffice.org2.0/program that links against libXaw is pluginapp.bin. If you run comm against the list of symbols defined in libXaw, and the list of symbols required by pluginapp.bin, you find zero symbols in common. In other words, pluginapp.bin doesn't actually need to be linked against libXaw. Sorry about the phenomenal bug spam, guys. Adding xorg-team@ to the QA contact so bugs don't get lost in future. xaw8 is gone. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.