[csw-maintainers] Library problem?

[Mike Watters]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

William Bonnet wrote:
> Hi
> 
>> It would seem as though our existing users might be similarly plagued
>> with
>> this sort of thing if they upgraded recently.
>>
>> if so, this very nasty situation, warrants an email about it, to the
>> announce and user lists.
>>   
> Based on Trygve advices i made a few tests and had a look to the way
> sun's gnome desktop is working.  I run a Ultra 20, thus an amd64 CPU. In
> the Solaris installation there is both 32 and 64 bits versions of pango.
> Here are the files i have :
> 
> 64 bits version
> 
> [william at cyaegha:/usr/lib/amd64]$ ls *pango*
> libpango-1.0.so          libpangoft2-1.0.so         
> libpangox-1.0.so          libpangoxft-1.0.so
> libpango-1.0.so.0        libpangoft2-1.0.so.0       
> libpangox-1.0.so.0        libpangoxft-1.0.so.0
> libpango-1.0.so.0.501.1  libpangoft2-1.0.so.0.501.1 
> libpangox-1.0.so.0.501.1  libpangoxft-1.0.so.0.501.1
> 
> pango:
> 1.4.0
> 
> [william at cyaegha:/usr/lib/amd64]$ ls pango/1.4.0/modules/
> pango-arabic-fc.so  pango-basic-fc.so  pango-basic-x.so 
> pango-hangul-fc.so  pango-hebrew-fc.so  pango-indic-fc.so  pango-thai-fc.so
> 
> 32 bits version
> 
> [william at cyaegha:/usr/lib]$ ls *pango*
> libpango-1.0.so          libpangoft2-1.0.so         
> libpangox-1.0.so          libpangoxft-1.0.so
> libpango-1.0.so.0        libpangoft2-1.0.so.0       
> libpangox-1.0.so.0        libpangoxft-1.0.so.0
> libpango-1.0.so.0.501.1  libpangoft2-1.0.so.0.501.1 
> libpangox-1.0.so.0.501.1  libpangoxft-1.0.so.0.501.1
> 
> pango:
> 1.4.0
> 
> [william at cyaegha:/usr/lib]$ ls pango/1.4.0/modules/
> pango-arabic-fc.so  pango-basic-fc.so  pango-basic-x.so 
> pango-hangul-fc.so  pango-hebrew-fc.so  pango-indic-fc.so  pango-thai-fc.so
> 
> By default /etc/pango/pango.modules contains the 32 bits modules, even
> on my amd64 version.
> 
> I made the following tests running both 32 bits and 64 bits version of
> gtk-demo (/usr/bin/gtk-demo and /usr/bin/amd64/gtk-demo).
> 
> . Running application gtk-demo and pango.modules using same versions
> (both 32 or both 64 bits) work is fine.
> 
> . Running 64bits apps with 32 bits modules works also, but running 32
> bits app with 64 bits modules does not work.
> 
> Please notice that from Sun's isntallation running both 64bits, or
> 64bits apps with 32bits modules produce the same warnings
> 
>     (gtk-demo:19058): Gtk-WARNING **: Unable to locate theme engine in
> module_path: "blueprint",
> 
> Running a full 32bits stack produce no warnings
> 
> 
> 
> So i may suggest to do some more testing, like recompiling a couple of
> our desktop app in 64 bits mode, and test these apps against 32 bits
> modules. If it work fine, we may generate by default a pango.module
> config file containing 32 bits modules.
> 
> Because :
> 
> 1/ it works :)
> 
> 2/ most of the desktop app are compiled only in 32 bits
> 
> cheers
> W.
> 
> 

I believe the running proposal is to remove the isaexec from pango, and have
the default pango.modules file containing the 32bit.

there was some discussion on having a /opt/csw/etc/64/pango.modules file
which would be fine with me, AFAIK there is currently nothing in CSW that uses
the 64bit pango libs. ( as they never existed before ) so we can patch the
64bit versions to use the correct modules file.

I believe I saw some messages that Dago is on Holiday?


- --

Thanks,
Mike

"Any intelligent fool can make things bigger, more complex,
and more violent.  It takes a touch of genius -- and a lot of courage --
to move in the opposite direction."

* Albert Einstein 1879 - 1955
    US German-born Theoretical Physicist
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (SunOS)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkpVC5YACgkQLrhmsXMSLxftaQCfccWs8VOp5ZFYtdz/Y6r6CeSV
xe8An0qHVjDu+T8t1lBKs7q1lES9IfhT
=FEmQ
-----END PGP SIGNATURE-----