On 2012-06-10, Hartmut Figge <[email protected]> wrote: > Jochen Roderburg: > >>I have installed SM in /usr1/seamonkey210 and start with >>/usr1/seamonkey210/seamonkey >> >>XPCOMGlueLoad error for file /usr1/seamonkey210/libxpcom.so: >>libxul.so: cannot open shared object file: No such file or directory >>Couldn't load XPCOM. > > Normally extracting the .tar.bz2 in /usr1/seamonkey210 would create the > subdirectory seamonkey with the content of the .tar.bz2 and SM would be > started with /usr1/seamonkey210/seamonkey/seamonkey. > > But it is possible to avoid this subdirectory. I have now created > /usr1/seamonkey210 and copied the content of my existing installation of r> SM 2.10 from ~/seam/release/2.10/seamonkey to /usr1/seamonkey210. > > Calling SM from an xterm gives > > hafi@i5_64 ~ $ /usr1/seamonkey210/seamonkey > Document http://www.heise.de/newsticker/ loaded successfully > NOTE: child process received `Goodbye', closing down > > SM has started normally. Then i loaded heise und then quit SM with ^q. I > could see no problems. What do you get when issuing this command? >
Perhaps you have the problematic Mozilla libraries (also) somewhere in your standard library load path. I don't, I have them only in the various Mozilla product directories. The old Mozilla startup scripts used to define all sorts of Library-Path environment variables pointing to the install directory, so the problem had not much chance to come up then. The scripts had OTOH another small glitch which I have patched for long times here. They silently assumed that the final program directory had the same name as the program: When the product was installed in somepath/somedir they tried to load the actiual program binary under the name somepath/somedir/somedir-bin. So I was not unhappy that they (starting with FF a while ago and now with TB/SM) got rid of these scripts, but something seems to be not correct in the actual implementation of the new startup programs in TB and SM. It is, btw, not so that the install directory is not used at all for the loading of dynamic libraries. Strace shows that a number of them are loaded correctly, only a few produce errors. Jochen Roderburg _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
