SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
I've been trying out the OOo 2.0 betas and release candidates by converting all of the RPMs (minus the desktop-integration packages) into one large slackware .tgz package. All of the packages after 1.9.125 (beta2) give me this error:
/opt/openoffice.org2.0/program/soffice.bin: error while loading shared libraries: libvcl680li.so: cannot open shared object file: No such file or directory
The file libvcl680li.so appears in 1.9.125 but isn't anywhere to be found in later versions, so I'm stuck using this version. Does anyone else have this problem?
I run rpm2tgz on the RPMs, then explodepkg and makepkg to create one superpackage.
what's wrong with stable?
2.0 is looking much better than 1.x. I'm looking for bugs to report so I'd like to try the latest version. The thing is, I can't find anybody else having this exact problem, so I'm not sure if it's a problem with OOo, with converting the RPMs, or if I have a bad configuration.
First it can't find the file "libvcl680li.so" so I symlink it to the one provided with 1.9.125. Now it complains about missing "libutl680li.so" and I do the same thing, then again for "libtl680li.so" and "libtk680li.so". Here's when I get a different error:
no suitable windowing system found, exiting.
The missing files don't appear in any of the packages after running rpm2tgz.
I had this line in /etc/fstab so that /tmp would be mounted in RAM. I guess rpm2tgz uses /tmp and it ran out of space when converting the packages without giving any error messages, leaving me a few files short.
The problem is probably because soffice (and other commands like swriter etc)
is not in your PATH.
try following from command line:
does it work?
After I installed Open Office 2.0.3,
i had to add location of OpenOffice executables/scripts to my path.
So i just added one line to my ~/.profile:
Now, if i do:
And swriter, and soffice and all other things work.