LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   OpenOffice 2.0 installation (https://www.linuxquestions.org/questions/slackware-14/openoffice-2-0-installation-375277/)

olivia.jensen@mcgill 10-20-2005 09:52 PM

OpenOffice 2.0 installation
 
I have downloaded the current distribution of OpenOffice 2.0. The old-style Linux-installer program is no longer included and worse than that, only *.rpm files are supplied. I went through my usual hack for when confronted by the dreadful RedHat package manager, converting the *.rpms to *.tgz and then installing these. I usually install with a "-root /usr/local" option because I don't want any installed software burrowing into my Slackware systems. This usually allows for much more portability on upgrades, too.

Following this approach, OpenOffice 2.0 is installed into /usr/local/opt/openoffice2.0 directory. I would normally, fix this by moving it up to /usr/local/openoffice2.0 and killing the ./opt subdirectory though now as I still use Gnome primarily and want KDE too, I've started moving KDE into /usr/local/opt and linking it to the /opt/kde directory. I guess I can start another subdirectory under /usr/local/opt for more clutter.

Unfortunately, it seems, many shared library files are not installed anywhere in the OpenOffice tree and are not among those standard with Slackware distributions -- any level. In previous versions of OpenOffice, many similar libraries were installed in the OpenOffice directory tree and properly linked. Using my hack, several libraries are not available and not linked.

Has anybody managed to load OpenOffice 2.0 and make this free software that seems to be worth about half its price load???

Olivia olivia.jensen@mcgill.ca

egag 10-20-2005 10:04 PM

Re: OpenOffice 2.0 installation
 
Quote:

Originally posted by olivia.jensen@mcgill
I have downloaded the current distribution of OpenOffice 2.0. The old-style Linux-installer program is no longer included and worse than that, only *.rpm files are supplied. I went through my usual hack for when confronted by the dreadful RedHat package manager, converting the *.rpms to *.tgz and then installing these. I usually install with a "-root /usr/local" option because I don't want any installed software burrowing into my Slackware systems. This usually allows for much more portability on upgrades, too.

Following this approach, OpenOffice 2.0 is installed into /usr/local/opt/openoffice2.0 directory. I would normally, fix this by moving it up to /usr/local/openoffice2.0 and killing the ./opt subdirectory though now as I still use Gnome primarily and want KDE too, I've started moving KDE into /usr/local/opt and linking it to the /opt/kde directory. I guess I can start another subdirectory under /usr/local/opt for more clutter.

Unfortunately, it seems, many shared library files are not installed anywhere in the OpenOffice tree and are not among those standard with Slackware distributions -- any level. In previous versions of OpenOffice, many similar libraries were installed in the OpenOffice directory tree and properly linked. Using my hack, several libraries are not available and not linked.

Has anybody managed to load OpenOffice 2.0 and make this free software that seems to be worth about half its price load???

Olivia olivia.jensen@mcgill.ca

you've made a mess.
just move back kde where it should be and reinstall oo ( without a prefix).
it'll go to /opt and that's ok.

egag

reddazz 10-20-2005 11:24 PM

/opt is meant for third party applications (usually commercial ones), so its alright for openoffice to be installed there.

mjjzf 10-21-2005 04:00 AM

Actually, I'd say /opt is the correct place for it, from the directory definitions.

KMcD 10-21-2005 04:36 AM

why not use the ooo.SlackBuild from here, works for me.

Download the file ooo.SlackBuild and make it executable
Code:

chmod +x ooo.SlackBuild
. Then make a directory slack-desc
Code:

mkdir slack-desc
and download the package descriptions from the equivalent folder on that page and save them in the new folder. Then move the file OOo_2.0.0_LinuxIntel_install.tar.gz to the folder with ooo.SlackBuild in and run the script
Code:

./ooo.SlackBuild
and a few minutes later you'll have all the packages in the /tmp directory ready to be installed using installpkg.

Oh, you need to run the script as root. This thread will have more information.

cathectic 10-21-2005 06:02 AM

OOo 2.0.0 SlackBuild out
 
I have now updated the SlackBuild, so you don't need to edit it for use with OOo 2.0 - as per usual, latest version is available from here: http://slackbuild.strangeworlds.co.uk/ooo

Updated OOo language pack SlackBuild (edit as need be for the language pack you want to convert):
http://slackbuild.strangeworlds.co.uk/ooo-langpack

NOTE FOR 1.9.x to 2.0 users:
To anyone upgrading from the earlier development builds, I have renamed the menu package from openoffice.org-menus to openoffice.org-slackware-menus, so be aware that you will manually need to remove the old menus package and install slackware-menus if you are running upgradepkg. You will also need to update your slack-desc directory with the SlackBuild (slack-desc.menus has been replaced with slack-desc.slackware-menus).

Olivia:
As has already been said, please don't go mucking about with /opt - it's exactly where KDE wants to install itself by default, and hence Pat installs it there. It is other distributions that try to shoehorn it into /usr, not vice versa.

KMcD 10-21-2005 07:02 AM

Re: OOo 2.0.0 SlackBuild out
 
Quote:

Originally posted by cathectic
NOTE FOR 1.9.x to 2.0 users:
To anyone upgrading from the earlier development builds, I have renamed the menu package from openoffice.org-menus to openoffice.org-slackware-menus, so be aware that you will manually need to remove the old menus package and install slackware-menus if you are running upgradepkg. You will also need to update your slack-desc directory with the SlackBuild (slack-desc.menus has been replaced with slack-desc.slackware-menus).
Hi. The program itself is working well but the menus are causing probs. At first I didn't notice the name change but then corrected it. Menu entries were not there. I then removed all the packages and the reinstalled, no change. The software works and edited the Kmenu to add them manually but would really like to have the proper menu entries. Is there anything I should try.

Thanks again for a great slackbuild.

cathectic 10-21-2005 08:33 AM

Before you install it, check the openoffice.org-slackware-menus-2.0.0-i586-3.tgz package (run 'less openoffice.org-slackware-menus-2.0.0-i586-3.tgz' to make sure it isn't empty - you could also explodepkg it somewhere and check that everything is in order.)

After installing that package and the rest of OOo, run 'ls -l /usr/share/applications/openoffice*' and check the results - if the symlinks are there, they should be pointing to the correct entries in /opt (in a nice turqoise colour - if they're coloured red, then they're symlinking to something that doesn't exist). Also, make sure that in /usr/bin you have a shell script called openoffice.org-2.0 (not openoffice.org-1.9)

If however the openoffice*.desktop symlinks in /usr/share/applications are *not* there, or you're missing the relevant scripts in /usr/bin, please let me know ASAP (and any odd errors that pop up when running the SlackBuild - besides "unable to create /tmp/package, directory already exists", since I know about that and it's nothing to worry about) and I'll see if I fix it (as it runs fine on two different machines here and produces working menus, I'm at a bit of a loss as to why the menu entries aren't showing up on your end, unless Kmenu is being difficult?).

KMcD 10-21-2005 09:15 AM

Quote:

Originally posted by cathectic
After installing that package and the rest of OOo, run 'ls -l /usr/share/applications/openoffice*' and check the results - if the symlinks are there, they should be pointing to the correct entries in /opt (in a nice turqoise colour - if they're coloured red, then they're symlinking to something that doesn't exist). Also, make sure that in /usr/bin you have a shell script called openoffice.org-2.0 (not openoffice.org-1.9)
symlinks are broken, script openoffice.org-2.0 is in /usr/bin, so the prob is with the symlinks.

olivia.jensen@mcgill 10-21-2005 02:07 PM

Re: OOo 2.0.0 SlackBuild out
 
Quote:

Originally posted by cathectic
I have now updated the SlackBuild, so you don't need to edit it for use with OOo 2.0 - as per usual, latest version is available from here: http://slackbuild.strangeworlds.co.uk/ooo

Updated OOo language pack SlackBuild (edit as need be for the language pack you want to convert):
http://slackbuild.strangeworlds.co.uk/ooo-langpack

NOTE FOR 1.9.x to 2.0 users:
To anyone upgrading from the earlier development builds, I have renamed the menu package from openoffice.org-menus to openoffice.org-slackware-menus, so be aware that you will manually need to remove the old menus package and install slackware-menus if you are running upgradepkg. You will also need to update your slack-desc directory with the SlackBuild (slack-desc.menus has been replaced with slack-desc.slackware-menus).

Olivia:
As has already been said, please don't go mucking about with /opt - it's exactly where KDE wants to install itself by default, and hence Pat installs it there. It is other distributions that try to shoehorn it into /usr, not vice versa.

Carlos,

I don't want KDE at all... If I have to use KDE in order to run OpenOffice, then even for free, I don't want OpenOffice. When installed using SlackBuild and last night's download, a whole swat of library files seem to be missing... Some of this might be due to my not running the most recent versions of gcc libraries but I'm quite sure that some of them should have been included in the OpenOffice download.

This release of OpenOffice is conceptually ugly from my point of view.... It seems to be very, very machine and OS level dependent and then why the hell would anyone abandon Micro$oft just to tangle into another model with all the "imposed requirements" that Micro$oft obliges.?

_______________________________________________________________________________

$ ./soffice
/opt/openoffice.org2.0/program/javaldx: error while loading shared libraries: libuno_sal.so.3: cannot open shared object file: No such file or directory
/opt/openoffice.org2.0/program/pagein: error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory
/opt/openoffice.org2.0/program/soffice.bin: error while loading shared libraries: libvcl680li.so: cannot open shared object file: No such file or directory

$ ldd ./soffice.bin
libvcl680li.so => not found
libsvl680li.so => not found
libsvt680li.so => not found
libutl680li.so => not found
libtl680li.so => not found
libcomphelp4gcc3.so => not found
libucbhelper3gcc3.so => not found
libvos3gcc3.so => not found
libuno_cppuhelpergcc3.so.3 => not found
libuno_cppu.so.3 => not found
libuno_sal.so.3 => not found
libtk680li.so => not found
libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0x4002a000)
libSM.so.6 => /usr/X11R6/lib/libSM.so.6 (0x40038000)
libICE.so.6 => /usr/X11R6/lib/libICE.so.6 (0x40041000)
libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x40058000)
libdl.so.2 => /lib/libdl.so.2 (0x4011f000)
libpthread.so.0 => /lib/libpthread.so.0 (0x40122000)
libstlport_gcc.so => not found
libstdc++.so.6 => not found
libm.so.6 => /lib/libm.so.6 (0x40174000)
libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x40197000)
libc.so.6 => /lib/libc.so.6 (0x4019f000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)

$
______________________________________________________________________________

bmfan 10-21-2005 02:17 PM

looks to me like you've really screwed up your slackware install

cathectic 10-21-2005 06:48 PM

KMcD:

Explodepkg the openoffice.org-slackware-menus package somewhere, and check install/doinst.sh - does it exist, and does it contain the commands to create the symlinks?

Olivia:

You don't need KDE for OpenOffice 2.0, I was simply making the point that you really shouldn't be trying to shoehorn it into somewhere that it doesn't belong.

All of those libraries (except for one) should be included in the openoffice.org-core package - if the openoffice.org-core package produced by the SlackBuild is not 84MB big, then it hasn't converted properly - check that you have enough free hard drive space in /tmp before running the script, it's the most likely cause of failure.

libstdc++.so.6 - are you running GCC 3.4 from /testing? Either reinstall GCC, or downgrade back to GCC 3.3.4 which ships by default with Slackware.

egag 10-21-2005 09:22 PM

i only used :
#rpm2tgz *.rpm
#installpkg *.tgz

then run : /opt/openoffice.org2.0/program/soffice ( as user )
and it gives the opening screen ( ask to register etc.. )
seems to work ok, so ...am i missing something ?

egag

titopoquito 10-22-2005 04:04 AM

Re: OOo 2.0.0 SlackBuild out
 
Quote:

Originally posted by cathectic
as per usual, latest version is available from here: http://slackbuild.strangeworlds.co.uk/ooo

Looking at the script I noticed a little typo, a missing space in the line:
Code:

( if which update-mime-database; then update-mime-database/usr/share/mime; fi ) &> /dev/null
I think there should be an extra space after the second "update-mime-database", else at least GNOME should have problems handling the file types correctly.

Edit: Typo

titopoquito 10-22-2005 04:06 AM

Oh, and thank you for the buildscript :D


All times are GMT -5. The time now is 05:19 AM.