[SOLVED] Slackware 13 64bit: First time using SlackBuilds and unable to install programs.

Switch7 · 10-03-2009, 09:31 PM

I never used SlackBuilds before and I tried to install programs by using with it. I read the HOWTO but I never gotten it to work. I did a forum search and found this thread: http://www.linuxquestions.org/questi...ht=slackbuilds

Quote:

1. Download the slack.Build script for your program (someprogram) you want to install. untar the script: tar -xzvf someprogram.tar.gz
You will now have a directory called someprogram in your build directory. Download the source for someprogram. Move the source inside the some program directory. cd into that directory.
2. Inside the someprogram directory there will be a build script called someprogram.SlackBuild.
3. Become root type su, enter root password
4. Type #chmod +x someprogram.SlackBuild
5. Execute the build script by #./someprogram.SlackBuild
6. Sit back and watch as your slackware package is created.
7. cd /tmp
8. #installpkg somperogram-i486_SBo.tgz

Quote:

Originally Posted by rworkman

Er, I see now that you already referenced the HOWTO. Hmmm...

If you're trying to build scribus, then here's your steps:
1. Download http://slackbuilds.org/slackbuilds/1...scribus.tar.gz

Code:

wget http://slackbuilds.org/slackbuilds/12.0/office/scribus.tar.gz

2. Extract the script tarball.

Code:

tar -xzf scribus.tar.gz

3. Change directory to inside the name of the app (scribus in this case).

Code:

cd scribus

4. Download the source code for the app. There are at least two ways to do this:

Code:

wget $( grep DOWNLOAD scribus.info | cut -d = -f 2 )

OR get the download link from the SlackBuilds.org scribus page

Code:

wget http://dl.sourceforge.net/scribus/scribus-1.3.3.9.tar.bz2

5. Run the SlackBuild script.

Code:

./scribus.SlackBuild

Note that you can alter the ARCH, BUILD, or TAG variables directly from the command line (without editing the script), although in the case of ARCH, you do have to pass a valid value.
Some scripts also include other variables that can be passed from the command line, and those are mentioned in the README files for those scripts. The way to do this is as follows - for example, if I want to build scribus with i686 ARCH, package BUILD number 2, and with my initials as the build TAG, I would do this:

Code:

ARCH=i686 BUILD=2 TAG=_rlw ./scribus.SlackBuild

One last point (for those who are not aware) - we have an easy method of obtaining script tarballs for things that we host. All of the tarballs are available by name from http://slackbuilds.org/ports/$SLACK_VERSION/$APP.tar.gz
For example:

Code:

wget http://slackbuilds.org/ports/12.0/scribus.tar.gz

EDIT (late addition):
Now after taking all this time to type this, I see that hitest has beaten me :-)

I tried it for various programs like openbox, rxvt-unicode, conky, etc. but never succeeded on any.

I tried to follow it in a similar fashion for openbox but I was unable to install it. This was the exact way I tried it.

1. # wget http://slackbuilds.org/slackbuilds/1...openbox.tar.gz
2.

Code:

bash-3.1# tar xzf openbox.tar.gz
bash-3.1# cd openbox
bash-3.1# wget http://icculus.org/openbox/releases/openbox-3.4.7.2.tar.gz

3. # ./openbox.SlackBuild
(long list of package was created)

4. # cd /tmp
5. # installpkg openbox-i486_SBo.tgz

It's fine until cd /tmp but after I try to do the installpkg, it says file not found. It would greatly be appreciated if anyone could tell me what I'm doing wrong.

~sHyLoCk~ · 10-03-2009, 09:58 PM

After you compile using ./openbox.Slackbuild does it say the package has been created in /tmp ?
Btw, you can use sbopkg for easily installing stuffs from slackbuilds.

Switch7 · 10-03-2009, 10:09 PM

Quote:

Originally Posted by ~sHyLoCk~

After you compile using ./openbox.Slackbuild does it say the package has been created in /tmp ?
Btw, you can use sbopkg for easily installing stuffs from slackbuilds.

I'm not sure (exited out xterm and lost log) if it said it was created in tmp but when I type find /tmp in terminal , I get: /tmp/SBo/openbox-3.4.7.2 and a very long list like

/tmp/SBo/openbox-3.4.7.2/mp4
/tmp/SBo/openbox-3.4.7.2/mp4/lib-link.m4
/tmp/SBo/openbox-3.4.7.2/mp4/inttypes_h.m4
/tmp/SBo/package-openbox
etc.
etc.

Thank you for the link, I'll check that out.

mudangel · 10-03-2009, 10:15 PM

did you try ARCH=x86_64, or changing ARCH=${ARCH:-i486(or -i686)} to ARCH=${ARCH:-x86_64} in the SlackBuild?

Switch7 · 10-03-2009, 10:33 PM

Quote:

Originally Posted by mudangel

did you try ARCH=x86_64, or changing ARCH=${ARCH:-i486(or -i686)} to ARCH=${ARCH:-x86_64} in the SlackBuild?

I never tried that. It wasn't listed on howto or those examples but I guess that was the main problem. What I said in the first post was the exact way I did it. I just typed those in terminal, wait until it finished and typed it exactly again in those order. For some reason, I have a feeling I'm still missing something.

This should the correct way?

1. # wget http://slackbuilds.org/slackbuilds/1...openbox.tar.gz
2.

Code:

bash-3.1# tar xzf openbox.tar.gz
bash-3.1# cd openbox
bash-3.1# wget http://icculus.org/openbox/releases/openbox-3.4.7.2.tar.gz

3. # ARCH=x86_64 ./openbox.SlackBuild
4. # cd /tmp
5. # installpkg openbox-i486_SBo.tgz

This is my first time installing it so I'm a bit worried if I did it correctly on the change directory (cd openbox).

Code:

bash-3.1# tar xzf openbox.tar.gz
bash-3.1# cd openbox
bash-3.1# wget http://icculus.org/openbox/releases/openbox-3.4.7.2.tar.gz

When I type: cd openbox in terminal as you can see above, it doesn't say anything about directory changed. It just gives me:

Code:

bash-3.1#

again right after I typed it. Am I worrying too much or is this normal?

mudangel · 10-03-2009, 10:41 PM

Yeah, unless you set up your .bashrc(or is it .bash_profile?) to display your current directory, it just gives you a prompt. If you want to see where you are, try "pwd"-that will tell you what the current directory is(pwd=print working directory).

Switch7 · 10-03-2009, 10:51 PM

Quote:

Originally Posted by mudangel

did you try ARCH=x86_64, or changing ARCH=${ARCH:-i486(or -i686)} to ARCH=${ARCH:-x86_64} in the SlackBuild?

After I added this in, I got

Code:

Slackware package /tmp/openbox-3.4.7.2-x86_64-5_SBo.tgz created.

After that, I typed this and got:

Code:

# cd /tmp
# installpkg open-box-i486_SBo.tgz
Cannot install open-box-i486_SBo.tgz: File not found

I'm guessing I need to do

installpkg openbox-3.4.7.2-x86_64-5_SBo.tgz

instead. I'm just making sure before I mess up my computer again.

~sHyLoCk~ · 10-03-2009, 10:54 PM

Try this:

installpkg /tmp/openbox-3.4.7.2-x86_64-5_SBo.tgz

You are giving the wrong package name. :P May I suggest using tab completion?

mudangel · 10-03-2009, 11:00 PM

Ha ha, ~sHyLoCk~ beat me to it! Tab completion is very handy, especially for lazy typists(such as myself)!

Switch7 · 10-03-2009, 11:18 PM

Thank you very much everyone! It worked perfectly. However, I'm having trouble switching to openbox. I did a google search and found out I need to type "openbox --replace"

I'm not able to switch since it says windows manager is already running on screen 0. I'm currently on fluxbox and going from fluxbox menu > windows mangagers > switch to another windows doesn't give me any error. Sorry, this is most likely my last question before thread is solved. I'm not sure how to add these new programs to where I can open it up or for example, the terminal like rxvt, I can only open it from using xterm. When I close xterm, rxvt closes too.

~sHyLoCk~ · 10-03-2009, 11:24 PM

You can't use openbox within fluxbox. Both are WMs. You can use openbox within a DE like KDE, gnome or a well-customized openbox DE-> LXDE [I would recommend you this, get it from alien's package] and also you can use openbox standalone. From KDM, select sesion and change to openbox.

Good Luck

mudangel · 10-03-2009, 11:29 PM

If you're in runlevel 3(that is, you type "startx" to get to X), try "xwmconfig"- it'll give you options regarding your choice of window manager/desktop...just curious, if you're using Fluxbox(which I use, and love, so I'm biased ;^), why do you want Openbox?

Switch7 · 10-03-2009, 11:51 PM

Quote:

Originally Posted by mudangel

If you're in runlevel 3(that is, you type "startx" to get to X), try "xwmconfig"- it'll give you options regarding your choice of window manager/desktop...just curious, if you're using Fluxbox(which I use, and love, so I'm biased ;^), why do you want Openbox?

Thank you, it worked great.

I was just trying out other random WM, I wasn't specifically looking at OpenBox. The reason I was looking for other WM was because of fluxbox's (taskbar?) on the bottom being half the size of my screen in the center. I was looking for something that has the taskbar stretched out in the entire screen. Maybe this is just limited knowledge since the look I was trying to get is this http://www.box-look.org/content/show...?content=61999 and this person uses fluxbox. I followed the instruction, only the color changed and the taskbar remained the same.

BrZ · 10-03-2009, 11:57 PM

Normally the procedure is just changing the version number and setting it to 64bit. It is easy, until the build fail... And some are really tricky =]

You can start from the ground with Alien's SlackBuild Toolkit (alien.slackbook.org/AST/) or get a lot of them on SlackBuilds main site (slackbuilds.org).

There are trusted precompiled binaries for Slackware64. Openbox sits here: http://connie.slackware.com/~alien/s...ox/pkg64/13.0/

Another nice set of 64bit packages are stored at http://rlworkman.net/pkgs/13.0/x86_64/

SlackBook (www.slackbook.org), SlackWiki (http://slackwiki.org/) and Alien's Wiki (http://alien.slackbook.org/dokuwiki/...ware:slackware) are nice places to read about Slackware.

mudangel · 10-03-2009, 11:58 PM

Oh yes, you can make Fluxbox do lots of stuff- I have my taskbar on top, full width, and hidden 'til I move the cursor to the top of the screen. I also have a semi-transparent menu and urxvt. I really like the way the menu file works, too- very easy to change it to suit your preference! The apps and keys files are pretty useful, as well, and easy enough to work with.