I've been experimenting with seamonky2 and seem ot have a problem with
Xulrunner.
After building I checked the executable:
bdu...@core2:/tmp/seamonkey/seamonkey-build/suite/app$ ldd seamonkey-bin
linux-vdso.so.1 => (0x00007fffdcfff000)
libpthread.so.0 => /lib/libpthread.so.0 (0x00007f5fe2694000)
libmozjs.so => not found
libxul.so => not found
libxpcom.so => not found
libxpcom_core.so => not found
libplds4.so => /usr/lib/libplds4.so (0x00007f5fe2491000)
libplc4.so => /usr/lib/libplc4.so (0x00007f5fe228d000)
libnspr4.so => /usr/lib/libnspr4.so (0x00007f5fe2052000)
...
When I installed Xulrunner-1.9.1.2, I went by the current instructions but I
note that some libraries not accessible:
bdu...@core2:/tmp/seamonkey/seamonkey-build/suite/app$ ls
/usr/lib/xulrunner-1.9.1.2/*so
libfreebl3.so
libplc4.so*
libmozjs.so
libplds4.so
libnspr4.so*
libsmime3.so*
libnss3.so*
libsoftokn3.so*
libnssckbi.so
libssl3.so*
libnssdbm3.so
libxpcom.so
libnssutil3.so*
libxul.so
The ones marked with an asterisk are linked back to /usr/lib, but the others
are
not. Therefore I don't think firefox/thunderbird/seamonky are finding
libmozjs.so, libxul.so, libxpcom.so. libxpcom_core.so is found in
/usr/lib/seamonkey-2.0.
The curious thing is that seamonkey seems to run just fine without finding
these
libraries. Should we making links to the other libraries?
Comments?
-- Bruce
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
