Slackware :: Run Openoffice.org.SlackBuild As Root Within The /tmp Directory?
Apr 9, 2010
I downloaded and extracted office slackbuild. Then tried to run openoffice.org.SlackBuild as root within the /tmp directory. Can anyone help?
Code:
siawacsh@zorro:~/Downloads/office/openoffice.org$ ls
OOo_3.2.0_LinuxX86-64_install_wJRE_en-US.tar.gz README doinst.sh openoffice.org.SlackBuild* openoffice.org.info slack-desc
siawacsh@zorro:~/Downloads/office/openoffice.org$ su
Password:
root@zorro:/home/siawacsh/Downloads/office/openoffice.org# ./openoffice.org.SlackBuild
tar: /home/siawacsh/Downloads/office/openoffice.org/OOo_3.2.0_LinuxIntel_install_en-US.tar.gz: Cannot open: No such file or directory
I have downloaded the source package and the slackbuild package for OpenOffice 3.2.0.Everything seems to go well until doinst, then I get error messages about zero length files:
I downloaded the slackbuilds openoffice.org files, extracted them, added the original source, ran chmod +x openoffice.org.SlackBuild, ran ./openoffice.org.SlackBuild, then found the resulting .tgz and installpkg'ed it. I was able to get through all of the steps listed without any error messages and everything seemed to be going well. However, now when I navigate to opt/openoffice.org3 (the created folder) and attempt to run any of the programs from kde nothing happens. When I attempt to run them in terminal I get the following message:
root@slacktop:~# soffice /usr/bin/soffice: line 98: /opt/openoffice.org3/program/../basis-link/program/pagein: No such file or directory /usr/bin/soffice: line 104: /opt/openoffice.org3/program/../basis-link/ure-link/bin/javaldx: No such file or directory /usr/bin/soffice: line 129: /opt/openoffice.org3/program/soffice.bin: No such file or directory
is there some reason these files wouldn't be in there after a normal installation? I read the howto on slackbuilds.org several times to make sure I got all the steps right, and have tried uninstalling with removepkg and reinstalling and the same thing keeps happening.
I have used a couple of slackbuild binary packages (i.e. without doing the actually build) and have worked fine. Thanks to those who have spent the time and effort to create them.
When installing the package I wanted to know what binary files were being put on my machine and at which directory location. This was more out of curiosity.
However, now I plan to get the boost slackbuild package. It's more relevant to know where it's being installed. Is there a way to know that? Also, can I specify a different directory?
I installed Slackware 13.37 and when i configured the LAMP, I now have a file session_mm_apache2handler0.sem in root(/) directory. I searched in the internet and found this:
Im trying to install topolight in my slackare 13 virtual box, I downloaded the tar file and when I try and decompress it doesnt decompress root@me:/home/Italy# tar -xzf typolight-2.8.3.tar.gz and how do I get to my toplolight root directory than.
I have an nfs share that mounts automatically when kde starts.
Code:
wendy@DellNB:~$ cat .kde/Autostart/mountNAS.sh #!/bin/bash mount ~/TestShare #echo "NAS Mounted"
[code]...
Gimp works fine editing and saving photos from/to the nfs share. kWrite can do its thing and read/create files on the NAS. Files I create with vim are visible and editable under windows. OpenOffice however, when I try an open a file I get "file is locked by unknown user." I open as copy and try saving to the share with a different name... No Dice, error saving to share the file is created on the share but it is empty. I did some reading and found a post that said to comment a line from a file called soffice, which I cannot find.
I am going to try out a tiling wm and I have narrowed my search down to scrotwm and dwm. I installed scrotwm from slackbuilds.org but it did not show up as a selection when I ran xwmconfig? Any ideas as to why? So then I went install dwm from slackbuilds.org but saw there was only a build script for slackware 13 as opposed to 13.1 which is what I am running. So two questions for dwm, one why is there no slackbuild for 13.1, and two when I tried to use the slackbuild for 13 this also didn't show up under xwmconfig, any thoughts?
As always, very impressive effort from Slackbuilds.org to get slackbuild scripts updated for 13.1. Thanks to all who maintain these scripts. One which does not seem to have made it to 13.1 so far is a build script for WINE. Anybody know whether this is beacuse of some problem ? Or just an oversight ? The 13.0 script is there - might be OK to just use this with 13.1 ?
Getting the hang of diff and patch, to a small extent...However, I couldn't get the slack-desc to print anything useful when running installpkg. Always had trouble with the slack-desc files.
i keep getting this error during gecko-mediaplayer build running 1337 stable up to date. lang.sh has en us utf8 enabled, (it didn't work with en US either.
it seems that there is no x11vnc slackbuild on sbo for 13.1. just wondering if there is something else people use to share the :0 desktop, or should i start looking into the 13.0 slackbuild
At least, that is what I think happened.I was interested in trying out tilda, which needs the confuse libary, both of which are slackbuilds on slackbuilds.orgI built and installed confuse, and then went to build tilda but got some error I could not follow up on.However after this, nothing as a normal user would work!For some reason my libary directories, /lib64, /usr/lib64 and other key directories such as /usr/share and /usr/bin were set to have permissions 700It took me a while to figure out what was causing the problem.Can anyone confirm that the confuse slackbuild resets your permissions like this? Otherwise, what could have caused it?Can someone please give me the correct permissions for those direcories? Is it safe to just do chmod -R 755 /usr and /lib64?
I'm trying to install OpenShot for the second time. I was originally trying to make a slackbuild for this, when a new one appeared in SBo. It does not work for me, however. It seems that it has to run a python install script and this fails. The package then complains that it cannot find the mlt python bindings.
Im trying to recompile glibc from a working slackware-current system using source from a slackware mirror. I'm doing it for testing purpose only. Never done that before, so i'm not sure if i'm doing it right. I get the following error:
Code:
make[2]: Entering directory `/glibc-tmp-a44be92860d34519b0c9a4500878e2e6/glibc-2.11.1/iconvdata' ../Makeconfig:85: ../i486/config.make: No such file or directory /bin/sh: line 0: cd: ../i486: No such file or directory The GNU C library has not been configured.
I have the latest fbreader.Slackbuild via sbopkg. The compilation steps seem to run OK until, if I understand this correctly, it starts work on libzlcore, at which point things go wrong :
Code:
OK
The README says I will need liblinebreak, which I "Slackbuilt" with no problems.
I used the fbreader.SlackBuild in a 64bit system to create a package and I got some libraries installed under /usr/lib instead of /usr/lib64. FBReader seems to work fine though, so I'm not sure this is a problem. I guess it could be if some other app looks for those libraries. Just thought I should report it anyway.
Tried to compile kbluetooth using the SlackBuild and it was going well until it got to here,
[Code]...
The script was ran using Slackware64 13.37 and the 2.6.38.4 kernel. I've googled around and searched here, but haven't found anything "current" on the such a problem.
If 13.1 and KDE 4.4.3 aren't new enough for anyone, I've just successfully built and installed KDE 4.4.4 with the slackbuilds for 4.4.3. I had to edit the Slackbuild for kdenetwork by commenting out the line that patches the source. Other than that everything seems to be fine, although I don't know yet if this is a good thing or a bad thing since I've just got it installed.
I was trying to install the HandBrake slackbuild. It gave me an error saying it needed webkit, so I check for it in slackbuilds.org, where I found it. Listing said it required two things: libsoup and icu4c. So I downloaded the slackbuilds for those two and they installed fine, then started the install for webkit.
It did its build thing for about ten minutes, then it errors out, but the error message is pretty convoluted so I'm not sure what its telling me. Here's the last few lines from the terminal:
[Code]...
Anyone know what went wrong, and what I need to do to fix this?
On my ubuntu system when I was editing pdf files I used PDF-ShufflerSo now I wrote a slackbuild script for my slackware 13 (xfce)To be more specific, I dont know how to write a slackbuild script so I try to edit the pyPdf.SlackBuild script, hopefully it works! So I want to give it in public view maybe someone need it some time.
Running Slackware64-13.1; installed the SlackBuild Blender and I changed the last line in SlackBuild script to .txz everything seems fine. Now I'm looking at FlashPlayer SlackBuild, noticed the last line is .tgz? Just want to make sure I am supposed to be changing the last script line .tgz to .txz?
Where do slackbuild scripts put all their stuff? Because I was compiling QT4 with a slackbuild script and after like 10 years it finally got to the end I think and it was creating the tar.gz file in /tmp I think and then my stupid athlon overheated and my computer turned off. So I got an air compressor and blew all the dust out of the cooling fins and started over. But the script started completely over from the beginning like it hadn't done it all already.
My athlon's overheated before when compiling manually and when restarting make just skips all the files it already compiled. I wonder the slackbuild script doesn't do that.
