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.
Distribution: Slackware 13.0, Ubuntu 9.10, Windows XP Pro SP3
Posts: 100
Original Poster
Rep:
Code:
bash-3.1# chmod +x openoffice.org.SlackBuild
bash-3.1# sh openoffice.org.SlackBuild
gzip: stdin: unexpected end of file
tar: Child returned status 1
tar: Error exit delayed from previous errors
openoffice.org.SlackBuild: line 80: cd: /tmp/SBo//RPMS/: No such file or directory
bash-3.1#
I don't understand why am I getting these errors. Is it a bad file or something?
Moved: This thread is more suitable in Linux Distributions -> Slackware and has been moved accordingly to help your thread/question get the exposure it deserves.
You're getting that error because the OOo source file (which actually just contains binaries and not source code, but that is unimportant here) either does not exist or is corrupt. Try following these directions EXACTLY, starting from scratch, in a terminal (you must enter your root password when prompted after the `su` command):
Code:
$ cd
$ mkdir OOo
$ cd OOo
$ wget http://slackbuilds.org/slackbuilds/12.1/office/openoffice.org.tar.gz
$ tar -zxvf openoffice.org.tar.gz
$ cd openoffice.org
$ wget http://openoffice.osuosl.org/stable/2.4.1/OOo_2.4.1_LinuxIntel_install_en-US.tar.gz
$ chmod +x openoffice.org.SlackBuild
$ su
# umask 0022
# ./openoffice.org.SlackBuild
# installpkg /tmp/openoffice.org-2.4.1_en_US-i586-2_SBo.tgz
# exit
I think I have thought about basically everything that could go wrong. Note, however, that it takes a LOT of room to build this package -- almost 1 GB. It may error out if it runs out of room in /tmp. You can always tell the script to use another partition with more room if you need to, but that is beyond the scope of these intructions.
The $ and # at the start of each line should not be typed -- they're just there to remind you when you're a regular user ($) or root (#).
Also note that in the future it would be best to check the md5sum of the source file to make sure the download is not corrupt.
I just use RPM (which comes with Slackware) to install OxgenOffice Professional. OxygenOffice Professional is an enhanced version of OpenOffice.org that can, among other things, open and save docx files.
Specifically, I download the RPMs, cd to the directory and type:
Quote:
rpm --nodeps -ihv *.rpm
Then I edit /etc/profile to add the directory to the PATH.
Distribution: Slackware 13.0, Ubuntu 9.10, Windows XP Pro SP3
Posts: 100
Original Poster
Rep:
Quote:
Originally Posted by T3slider
You're getting that error because the OOo source file (which actually just contains binaries and not source code, but that is unimportant here) either does not exist or is corrupt. Try following these directions EXACTLY, starting from scratch, in a terminal (you must enter your root password when prompted after the `su` command):
Code:
$ cd
$ mkdir OOo
$ cd OOo
$ wget http://slackbuilds.org/slackbuilds/12.1/office/openoffice.org.tar.gz
$ tar -zxvf openoffice.org.tar.gz
$ cd openoffice.org
$ wget http://openoffice.osuosl.org/stable/2.4.1/OOo_2.4.1_LinuxIntel_install_en-US.tar.gz
$ chmod +x openoffice.org.SlackBuild
$ su
# umask 0022
# ./openoffice.org.SlackBuild
# installpkg /tmp/openoffice.org-2.4.1_en_US-i586-2_SBo.tgz
# exit
I think I have thought about basically everything that could go wrong. Note, however, that it takes a LOT of room to build this package -- almost 1 GB. It may error out if it runs out of room in /tmp. You can always tell the script to use another partition with more room if you need to, but that is beyond the scope of these intructions.
The $ and # at the start of each line should not be typed -- they're just there to remind you when you're a regular user ($) or root (#).
Also note that in the future it would be best to check the md5sum of the source file to make sure the download is not corrupt.
Distribution: Slackware 13.0, Ubuntu 9.10, Windows XP Pro SP3
Posts: 100
Original Poster
Rep:
How did you get the wget (slackbuild site) and all that? I tried doing it by getting the http and the file name together but i get an error
Trying to get compiz-fusion from slackbuilds. I used compiz-install.sh earlier which i flunked on. The emerald wouldnt work and the code to initiate it wont work on the Autostarted Applications menu.
So rather do it this way.
Last edited by mongoosecage; 06-29-2008 at 02:06 AM.
How did you get the wget (slackbuild site) and all that? I tried doing it by getting the http and the file name together but i get an error
Well, the wget thing was just to make sure you downloaded everything to the correct folders. It's not really necessary, and you can just download using Firefox or another browser if you want. Just make sure to download "emerald.tar.gz" first (under the text "Download SlackBuild:"), then extract it using `tar -zxvf emerald.tar.gz`, then cd into the folder it just created (it should be called emerald), and then download the source package (emerald-0.7.4.tar.gz) to the newly created emerald folder. Then do the remaining steps as explained above (`chmod +x emerald.SlackBuild`, etc.).
If you want to use wget to follow the EXACT same procedure, just go to the page on slackbuilds.org for emerald (http://slackbuilds.org/repository/12.1/desktop/emerald/), right-click on the desired link (for example, emerald.tar.gz) and select "Copy Link Location" in Firefox (or the equivalent command in another browser. It is called "Copy Link Address" in Opera and Konqueror, for example). You can use the middle-click button of your mouse if it has a scrollwheel to paste the result (or press Shift+Insert) in the terminal. You can generally follow the same procedure for the source file, but not always. For example, some projects hosted on sourceforge.net require you to visit their download page which will pop up a download link -- slackbuilds.org doesn't link directly to the file. In that case, you should probably just download the file manually to the proper directory.
In the end, the only important thing is that the source file (emerald-0.7.4.tar.gz) is in the same directory as the SlackBuild (emerald.SlackBuild).
Someone else sugested this on another thread (unfortunately I cannot locate the link for you now), but you could just download OO from Zenwalk and use pkgtool. The only difference I see is that you'll be loading "Zen OpenOffice" instead of "OpenOffice". But, you'll learn more doing it the right way that everyone else si showing you. But, if all else fails...
Someone else sugested this on another thread (unfortunately I cannot locate the link for you now), but you could just download OO from Zenwalk and use pkgtool. The only difference I see is that you'll be loading "Zen OpenOffice" instead of "OpenOffice". But, you'll learn more doing it the right way that everyone else si showing you. But, if all else fails...
I would be wary of doing that. Zenwalk != Slackware, and it's set up a little differently. Some packages won't work, and may overwrite Slackware things (though I doubt that would happen frequently). You'd be better off downloading ready-made Slackware packages from Alien Bob's repository or rworkman's repository. slacky.eu also has a lot of packages and SlackBuilds, but I would trust it a little less than the previously mentioned repositories (though you shouldn't have any problems using their packages). I would discourage the use of linuxpackages.net -- although there are reputable packagers out there, finding them takes experience. Also, linuxpackages.net does not always include SlackBuilds, so you're basically using blind faith that the application was built and packaged properly.
My repository of choice is slackbuilds.org (though it is only a repository of SlackBuilds and not pte-built packages).
I would be wary of doing that. Zenwalk != Slackware, and it's set up a little differently. Some packages won't work, and may overwrite Slackware things (though I doubt that would happen frequently). You'd be better off downloading ready-made Slackware packages from Alien Bob's repository or rworkman's repository. slacky.eu also has a lot of packages and SlackBuilds, but I would trust it a little less than the previously mentioned repositories (though you shouldn't have any problems using their packages). I would discourage the use of linuxpackages.net -- although there are reputable packagers out there, finding them takes experience. Also, linuxpackages.net does not always include SlackBuilds, so you're basically using blind faith that the application was built and packaged properly.
My repository of choice is slackbuilds.org (though it is only a repository of SlackBuilds and not pte-built packages).
I'm sure you're right. And I'm not certainly suggesting that Zenwalk = Slackware in all apps. But, I did download that Zenwalk OpenOffice pkg and install it on SW 12.1. It seems to be working perfectly. Even integrated into the menus.
Just a note, a pre-built package for OOo is available at rworkman's repository (linked in my previous post), so using Zenwalk, although convenient, isn't necessary.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.