Summary: | Cannot build own libX11.so on Solaris which uses Solaris locale objects | ||||||
---|---|---|---|---|---|---|---|
Product: | xorg | Reporter: | Roland Mainz <roland.mainz> | ||||
Component: | Lib/Xlib | Assignee: | Hidetoshi Tajima <yakiudon> | ||||
Status: | RESOLVED INVALID | QA Contact: | |||||
Severity: | normal | ||||||
Priority: | lowest | CC: | alan.coopersmith, erik.andren | ||||
Version: | git | ||||||
Hardware: | SPARC | ||||||
OS: | Solaris | ||||||
Whiteboard: | |||||||
i915 platform: | i915 features: | ||||||
Bug Depends on: | |||||||
Bug Blocks: | 669 | ||||||
Attachments: |
|
Description
Roland Mainz
2004-05-31 13:52:38 UTC
I know almost nothing about the i18n module code in libX11 in either Solaris or the X.Org tree - Toshi would be the person to ask about this. I'll have to give a try to see what's actually happening, but from the truss output, it goes to /usr/openwin/lib/locale/lib/common for Xi18n modules, but the right path is /usr/openwin/lib/locale/common (no 2nd 'lib'). Can you try to work out XlocaleDir setting or else to manage the path to be correct one? Created attachment 2630 [details] [review] introduce Xi18nLibDirName to be set in hosts.def There must be better way. Due to POSTLOCALEDIR= LibDirName in xc/lib/X11 and xc/lib/X11/xlibi18n/Xi18nLib.conf, Xi18n shared libraries built in Xorg workspace are installed in /usr/openwin/lib/locale/lib/common/ directory. This isn't good on Solaris, since the system pre-installed Xi18n libraries are in /usr/openwin/lib/locale/common. To hack this, we may use a specific configuration for Xi18n Library location, say, Xi18nLibDirName, and this should be given in host.def like: #define Xi18nLibDirName /* blank */ Then, xc/lib/X11/Imakefile and xc/lib/X11/xlibi18n/Xi18n.conf can be changed like https://bugs.freedesktop.org/attachment.cgi?id=2630. So, any progess on this bug? closing really old bug; iirc this is much better with modular anyway |
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.