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 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? hafi@i5_64 ~ $ ls /usr1/seamonkey210/ | egrep '(seam|libxp)' libxpcom.so seamonkey seamonkey-bin Hartmut _______________________________________________ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
