SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
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.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
and
su
pass
# installpkg openoffice-3.2.1.6-x86_64-1_mm.tgz
but show
Verifying package openoffice-3.2.1.6-x86_64-1_mm.tgz.
Installing package openoffice-3.2.1.6-x86_64-1_mm.tgz:
PACKAGE DESCRIPTION:
# openoffice (Open Source Office Suite)
#
# This is the version of OpenOffice available from go-oo.org. It is an
# enchanced version of the upstream OpenOffice.org source code.
#
# Homepage: http://www.go-oo.org/
#
Executing install script for openoffice-3.2.1.6-x86_64-1_mm.tgz.
usr/lib64/ooo-3.2/program/unopkg: line 81: /usr/lib64/ooo-3.2/program/../basis-link/ure-link/bin/javaldx: cannot execute binary file
usr/lib64/ooo-3.2/program/unopkg: line 101: /usr/lib64/ooo-3.2/program/unopkg.bin: cannot execute binary file
Package openoffice-3.2.1.6-x86_64-1_mm.tgz installed.
Hello. Welcome to LQ.
The version of OO that you installed (go-oo) is now merged with Libreoffice. Use this link to download Eric's LibreOffice package. It works very well with 13.1.
Regards,
Bill
OK, but that is still OpenOffice. In a lot of folks opinions, mine included, LibreOffice is better.
Regards,
Bill
Bill is probably right, but I'm still getting bugs with Libreoffice (funny-looking menus and my customizations not staying put from session to session). For the time being, I'm sticking with OpenOffice from Robby Workman's repository until another release or two of Libreoffice proves to me that it's stable and works 100%.
I actually make money writing magazine articles, so I need for my word processor to be absolutely reliable.
Libreoffice is probably the future, but for me, the present belongs to OpenOffice.
Not having any luck using the current Open Office (3.3.0) version and modifying the SlackBuild script to build a package based on the tar downloaded from Open Office.
I modified VERSION in the SlackBuild to reflect the newer tar, but no luck. When running the slackbuild script, I get:
mv: cannot stat `desktop-integration/openoffice.org3.3.0-freedesktop-menus-3.3.0-9502.noarch.rpm': No such file or directory
Not having any luck using the current Open Office (3.3.0) version and modifying the SlackBuild script to build a package based on the tar downloaded from Open Office.
I modified VERSION in the SlackBuild to reflect the newer tar, but no luck. When running the slackbuild script, I get:
mv: cannot stat `desktop-integration/openoffice.org3.3.0-freedesktop-menus-3.3.0-9502.noarch.rpm': No such file or directory
Any thoughts?
The revision number (here is 9502) is changed from version to version. To get the accurate number, you need to dig into the extracted folder, then change it accordingly in the SlackBuild.
usr/lib64/ooo-3.2/program/unopkg: line 81: /usr/lib64/ooo-3.2/program/../basis-link/ure-link/bin/javaldx: cannot execute binary file
usr/lib64/ooo-3.2/program/unopkg: line 101: /usr/lib64/ooo-3.2/program/unopkg.bin: cannot execute binary file
You are installing the 64bit package of OpenOffice It looks like you are running a 32bit version of Slackware, because the error "cannot execute binary file" is a typical symptom of this.
The revision number (here is 9502) is changed from version to version. To get the accurate number, you need to dig into the extracted folder, then change it accordingly in the SlackBuild.
Ahhh, it's all in the details. Many thanks for pointing this out...revision was 9556. Thanks.
apparently I am too swamp on my project management job that i pass this out.
Last night i formated my pc (fscked up the kde4) and it just feel simplier... now i have no office suite and a bunch of stuff to do... (netbook is kickin ass but there is a reason why i have a 64 bits desktop at home)
now the dilemma...
shall i keep fighting with openoffice slackbuild or just move on to libreoffice?
decisions.. decisions..decisions..
Last edited by unSpawn; 04-08-2011 at 09:18 PM.
Reason: /u/s/
wel
I've test it and it feels just like OpenOffice... Same bugs when opening MS Office documents (specially the docx and xlsx files)
anyways.. it does the job and taking into consideration that this is LIBRE (as in free) with no attach to any company or whatever... it is time for me to make a little donation.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.