LinuxQuestions.org
Visit the LQ Articles and Editorials section
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 02-21-2011, 09:20 PM   #31
linux/unix87
Member
 
Registered: Oct 2010
Posts: 190

Original Poster
Rep: Reputation: 6

Quote:
Originally Posted by dh2k View Post
Here is a very quick - and brief - slackbuild guide:

1>
download the slackbuild -
and source files


They contain folder(s) and files archived and compressed for convenient downloading (commonly referred to as, slang: 'tarballed', commonly with .tar.gz extension)

2>
decompress and extract the slackbuild using the right click menu using a dolphin or konqueror file-managers (or any other file-manager you wish to use)

or from a termimnal:
Code:
tar -zxvf app-name-.Slackbuild
(the switches/options above, -zxvf
- unzipped the tarball -z
- extract the tarball -x
- give us feedback on screen, verbosely -v
- do all this on the filename given -f)


3>
move the source file into the extracted slackbuild directory

4>
from a terminal as root user build the slackbuild package
Code:
./app-name-.Slackbuild
if this does not build then try making the file executable, as normal user,
Code:
chmod +x app-name-.Slackbuild
THIS IS NOT ALWAYS NECESSARY as most slackbuilds should already be executable - warning - some are not but in my experience only very few.


5>
install the package
when package has built you will see the software-package in /tmp, something like this will be displayed
Code:
/tmp/app-name-.txz
to be more exact something similar to this
Code:
Slackware package /tmp/broadcom-sta-5.100.82.38_2.6.29.6_smp-i486-1_SBo.tgz created.
as root user:
Code:
installpkg /tmp/app-name-.txz
done. - feel free to delete the source and slackbuild and source, compressed and also extracted folders/files, if you want - it is not necessary to keep them.

This is a very brief guide to building slackbuild software packages. Please refer to other links above in this thread for more scope on this subject if required.





so to summarise:
1> download the slackbuild -
and source files

2> decompress and extract the slackbuild
3> move the source file into the extracted slackbuild directory
4> build the slackbuild package
5> install the package
ok im using slackware 13.1 and i tried to decompress and extract with tar -zxvf broadcom-sta.tar and the error message was root@darkstar:~# tar -zxvf broadcom-sta.slackbuild
tar (child): broadcom-sta.slackbuild: Cannot open: No such file or directory
tar (child): Error is not recoverable: exiting now
tar: Child returned status 2
tar: Error is not recoverable: exiting now
root@darkstar:~# tar -zxvf broadcom-sta.tar.slackbuild
tar (child): broadcom-sta.tar.slackbuild: Cannot open: No such file or directory
tar (child): Error is not recoverable: exiting now
tar: Child returned status 2
tar: Error is not recoverable: exiting now
root@darkstar:~# tar -zxvf broadcom-sta.tar-.slackbuild
tar (child): broadcom-sta.tar-.slackbuild: Cannot open: No such file or directory
tar (child): Error is not recoverable: exiting now
tar: Child returned status 2
tar: Error is not recoverable: exiting now

I typed it different way the second time.Ityped it the way it showed on dolphin file manager to be, so what does this mean?
 
Old 02-21-2011, 10:23 PM   #32
harryhaller
Member
 
Registered: Sep 2004
Posts: 429

Rep: Reputation: Disabled
I think that should be broadcom-sta.tar.gz and not broadcom-sta.tar.

If you have a file called broadcom-sta.tar, then the command should be:
Code:
tar xvf broadcom-sta.tar
The "z" was for decompressig the broadcom-sta.tar.gz into broadcom-sta.tar and that's already been done - apparently.

You don't have to do
Code:
tar -zxvf broadcom-sta.slackbuild
- that is the script file for the build which, aong with some other files, was in the tar.gz file.

All you had to do was:
Code:
tar xzvf broadcom-sta.tar.gz
That will produce a directory -and you are done with "tar-ing"

Then you just move the source file into that directory, and run broadcom-sta.slackbuild from within that directory as root. That will produce a file in /tmp - it will tell you that at the end of the build - look at the messages.

That file in /tmp is the one you then install with installpkg.
 
Old 02-22-2011, 05:02 AM   #33
dh2k
Member
 
Registered: Jan 2006
Distribution: Slackware 13.0 (KDE 3.5.10 from 12.2; Xfce 4.6; Fluxbox); Slackware 13.1 (KDE 4.5)
Posts: 203

Rep: Reputation: 44
Quote:
Originally Posted by linux/unix87 View Post
root@darkstar:~# tar -zxvf broadcom-sta.slackbuild
tar (child): broadcom-sta.slackbuild: Cannot open: No such file or directory
.
.
.
I typed it different way the second time.Ityped it the way it showed on dolphin file manager to be, so what does this mean?
Again, watch your case sensitive typing, uppercase S in broadcom-sta.Slackbuild.

But don't untar this "tar -zxvf broadcom-sta.slackbuild"
that was my fault - I typoed - but I have edited and changed now.


1> You should untar (decompress and extract) "tar -zxvf broadcom-sta.tar.gz".

2> Move source file into the extracted "broadcom-sta/" folder: "mv /path/to/your/source-file/hybrid-portsrc_x86_32-v5_100_82_38.tar.gz /path/to/extracted/broadcom-sta/"
(assuming you are using a 32-bit based system)

3> Build the slackbuild as root to create the installable slackware software package "./broadcom-sta.Slackbuild" then
"installpkg /tmp/broadcom-sta-5.100.82.38_2.6.29.6_smp-i486-1_SBo.tgz".

I am using slackware-13.0 so the numbers in middle (*2.6.29.6_smp-i486*) WILL be different - they should be your kernel version.

NOTE:
You don't need to type everything - use the tab key in a terminal to autocomplete - you have made several typoes with your text you are entering - this will help avoid typoes,

terminal tips:
tab-key: autocomplete, if 2 or more options are available - double tap to show all available options.
commannd: "ls": list file/folders in your present working directory you are in.

Last edited by dh2k; 02-22-2011 at 09:47 AM.
 
Old 02-23-2011, 08:27 PM   #34
linux/unix87
Member
 
Registered: Oct 2010
Posts: 190

Original Poster
Rep: Reputation: 6
ok thanks im going to try that also im using a 64 bit sorry for not giving all the info i thought i did.
 
Old 02-23-2011, 08:46 PM   #35
linux/unix87
Member
 
Registered: Oct 2010
Posts: 190

Original Poster
Rep: Reputation: 6
ok well i tried tar -zxvf broadcom-sta.tar.gz and it showed me the same error message as before like on my first thread on page 3.

root@darkstar:~# tar -zxvf broadcom-sta.tar.gz
tar (child): broadcom-sta.tar.gz: Cannot open: No such file or directory
tar (child): Error is not recoverable: exiting now
tar: Child returned status 2
tar: Error is not recoverable: exiting now
root@darkstar:~# tar -zxvf broadcom-sta-.Slackbuild
tar (child): broadcom-sta-.Slackbuild: Cannot open: No such file or directory
tar (child): Error is not recoverable: exiting now
tar: Child returned status 2
tar: Error is not recoverable: exiting now
root@darkstar:~# tar -zxvf broadcom-sta.Slackbuild
tar (child): broadcom-sta.Slackbuild: Cannot open: No such file or directory
tar (child): Error is not recoverable: exiting now
tar: Child returned status 2
tar: Error is not recoverable: exiting now
 
Old 02-24-2011, 03:55 AM   #36
dh2k
Member
 
Registered: Jan 2006
Distribution: Slackware 13.0 (KDE 3.5.10 from 12.2; Xfce 4.6; Fluxbox); Slackware 13.1 (KDE 4.5)
Posts: 203

Rep: Reputation: 44
I pointed another slackware user to your original query (they had same problem and same wireless device) - they confirmed the software package the slackbuild creates got his wireless device working:

http://www.linuxquestions.org/questi...3/#post4269210

He followed the slackbuild advice and got this working.


You seem to be experiencing difficulties building the slackbuild so I will attempt to guide you through this - I apologise if it may sound patronising but just trying to lend assistance:


1>
Download slackbuild and source archive files:
http://slackbuilds.org/repository/13.../broadcom-sta/

Download SlackBuild:
broadcom-sta.tar.gz
http://slackbuilds.org/slackbuilds/1...com-sta.tar.gz

and as you have mentioned - you have 64bit system architecture,
Source Downloads (64bit):
hybrid-portsrc_x86_64-v5_100_82_38.tar.gz (cac172f7422fa43264049c7065fe21d6)
http://www.broadcom.com/docs/linux_s...0_82_38.tar.gz


2>
YOU MUST BE IN THE SAME Directory as downloaded files, to check at the terminal type "ls":
Code:
david@slackware13:~/Downloads/src/testing$ ls
broadcom-sta.tar.gz  hybrid-portsrc_x86_64-v5_100_82_38.tar.gz
david@slackware13:~/Downloads/src/testing$
If you do not see the above items - then navigate to where you downloaded the slackbuild and source archive files

3>
REMEMBER, AS I HAVE SAID BEFORE use the tab key for autocompletion in the terminal - if it is not autocompleting in the context of the present working directory, either the files are not there - or you are not there ;-)

Code:
tar -zxvf bro<HIT THE TAB KEY>
and this will appear:
Code:
tar -zxvf broadcom-sta.tar.gz


Code:
david@slackware13:~/Downloads/src/testing$ tar -zxvf broadcom-sta.tar.gz
broadcom-sta/
broadcom-sta/broadcom-sta.SlackBuild
broadcom-sta/README
broadcom-sta/doinst.sh
broadcom-sta/slack-desc
broadcom-sta/broadcom-sta.info
now you will see the decompressed and untar'red "broadcom-sta/" directory - use the list "ls" command to check:
Code:
david@slackware13:~/Downloads/src/testing$ ls
broadcom-sta/        hybrid-portsrc_x86_64-v5_100_82_38.tar.gz
broadcom-sta.tar.gz
david@slackware13:~/Downloads/src/testing$


4>
move the source archive into the newly untar'red "broadcom-sta/" folder:
Code:
mv h<HIT TAB KEY> ./b<HIT TAB KEY>


5>
Change directory into new "broadcom-sta/" directory:
Code:
cd b<HIT TAB KEY>


6>
As root user build the slackbuild:
Code:
./<HIT TAB KEY>

7>
then install the software package you have just built:
Code:
root@slackware13:PATH/TO/WHEREEVER# 
installpkg /t[HIT TAB KEY]/bro[HIT TAB KEY]
Code:
installpkg /tmp/broadcom-sta-5.100.82.38_2.6.29.6_smp-i486-1_SBo.tgz
REMEMBER THE NUMBERS IN THE MIDDLE (are my kernel version) 2.6.29.6_smp- for i486 system architecture - YOURS WILL BE DIFFERENT - and that is all quite fine/normal.

Follow the above and hopefully it has been clear enough
When building the untar'ring and building slackbuild - if you are not sure if you are in the correct directory then just check with the list command "ls" - it will output/show files/folders of the directory you ar presently working in.




From your output/code snippets it seems you're using root to do all this - nothing techinically wrong with that but not recommended for many reasons - it is good practise to be a normal user when possible and only switch user to root "su" when you need be root then "exit" back to normal user - they're terminal commands in the quote marks to do just that - BTW.

Last edited by dh2k; 02-24-2011 at 04:23 AM.
 
Old 02-24-2011, 07:00 AM   #37
colorpurple21859
Senior Member
 
Registered: Jan 2008
Location: florida
Distribution: slackware64-current, puppy, ubuntu
Posts: 1,344

Rep: Reputation: 184Reputation: 184
Quote:
root@darkstar:~# tar -zxvf broadcom-sta.Slackbuild
Unless the op copied the file to the top of his home directory, wouldn't the file be in /root/Downloads# Or /home/<user>/Downloads
 
Old 02-24-2011, 07:39 AM   #38
dh2k
Member
 
Registered: Jan 2006
Distribution: Slackware 13.0 (KDE 3.5.10 from 12.2; Xfce 4.6; Fluxbox); Slackware 13.1 (KDE 4.5)
Posts: 203

Rep: Reputation: 44
To build a slackware package it vital that one is working in the correct present working directory as the archived source-files/slackbuild folder/files.

If unsure use "ls" to list directory contents to check your present working directory type "pwd"

If one is not in the correct directory or one in unsure then expect your efforts to fail - make sure you are in the correct directrory where you have downloaded the above files -

Last edited by dh2k; 02-24-2011 at 07:48 AM.
 
Old 02-25-2011, 07:24 PM   #39
linux/unix87
Member
 
Registered: Oct 2010
Posts: 190

Original Poster
Rep: Reputation: 6
Quote:
Originally Posted by dh2k View Post
I pointed another slackware user to your original query (they had same problem and same wireless device) - they confirmed the software package the slackbuild creates got his wireless device working:

http://www.linuxquestions.org/questi...3/#post4269210

He followed the slackbuild advice and got this working.


You seem to be experiencing difficulties building the slackbuild so I will attempt to guide you through this - I apologise if it may sound patronising but just trying to lend assistance:


1>
Download slackbuild and source archive files:
http://slackbuilds.org/repository/13.../broadcom-sta/

Download SlackBuild:
broadcom-sta.tar.gz
http://slackbuilds.org/slackbuilds/1...com-sta.tar.gz

and as you have mentioned - you have 64bit system architecture,
Source Downloads (64bit):
hybrid-portsrc_x86_64-v5_100_82_38.tar.gz (cac172f7422fa43264049c7065fe21d6)
http://www.broadcom.com/docs/linux_s...0_82_38.tar.gz


2>
YOU MUST BE IN THE SAME Directory as downloaded files, to check at the terminal type "ls":
Code:
david@slackware13:~/Downloads/src/testing$ ls
broadcom-sta.tar.gz  hybrid-portsrc_x86_64-v5_100_82_38.tar.gz
david@slackware13:~/Downloads/src/testing$
If you do not see the above items - then navigate to where you downloaded the slackbuild and source archive files

3>
REMEMBER, AS I HAVE SAID BEFORE use the tab key for autocompletion in the terminal - if it is not autocompleting in the context of the present working directory, either the files are not there - or you are not there ;-)

Code:
tar -zxvf bro<HIT THE TAB KEY>
and this will appear:
Code:
tar -zxvf broadcom-sta.tar.gz


Code:
david@slackware13:~/Downloads/src/testing$ tar -zxvf broadcom-sta.tar.gz
broadcom-sta/
broadcom-sta/broadcom-sta.SlackBuild
broadcom-sta/README
broadcom-sta/doinst.sh
broadcom-sta/slack-desc
broadcom-sta/broadcom-sta.info
now you will see the decompressed and untar'red "broadcom-sta/" directory - use the list "ls" command to check:
Code:
david@slackware13:~/Downloads/src/testing$ ls
broadcom-sta/        hybrid-portsrc_x86_64-v5_100_82_38.tar.gz
broadcom-sta.tar.gz
david@slackware13:~/Downloads/src/testing$


4>
move the source archive into the newly untar'red "broadcom-sta/" folder:
Code:
mv h<HIT TAB KEY> ./b<HIT TAB KEY>


5>
Change directory into new "broadcom-sta/" directory:
Code:
cd b<HIT TAB KEY>


6>
As root user build the slackbuild:
Code:
./<HIT TAB KEY>

7>
then install the software package you have just built:
Code:
root@slackware13:PATH/TO/WHEREEVER# 
installpkg /t[HIT TAB KEY]/bro[HIT TAB KEY]
Code:
installpkg /tmp/broadcom-sta-5.100.82.38_2.6.29.6_smp-i486-1_SBo.tgz
REMEMBER THE NUMBERS IN THE MIDDLE (are my kernel version) 2.6.29.6_smp- for i486 system architecture - YOURS WILL BE DIFFERENT - and that is all quite fine/normal.

Follow the above and hopefully it has been clear enough
When building the untar'ring and building slackbuild - if you are not sure if you are in the correct directory then just check with the list command "ls" - it will output/show files/folders of the directory you ar presently working in.




From your output/code snippets it seems you're using root to do all this - nothing techinically wrong with that but not recommended for many reasons - it is good practise to be a normal user when possible and only switch user to root "su" when you need be root then "exit" back to normal user - they're terminal commands in the quote marks to do just that - BTW.
ok im stuck on number seven it says path to whereever what does that mean? do i put it somewhere?
 
Old 02-25-2011, 08:01 PM   #40
linux/unix87
Member
 
Registered: Oct 2010
Posts: 190

Original Poster
Rep: Reputation: 6
ok i think i screwed up on number 6 not 7 because i never really made it to 7. 6 says to be root user well from what i read from the directions. while your in broadcom-sta directory use root user am i correct? just type in ./ while in that directory ? cause i tried that and it doesnt work on tab key, by the way that is really usefull thanks for that. anyway is there a way you can show me what a slackbuild looks like not asking for the one im trying to do just an example if you dont care? i got everything done except for building the slackbuild and installing. ill give you what i got root@darkstar:~# ls
broadcom-sta.tar.gz* hybrid-portsrc_x86_64-v5_100_82_38.tar.gz*
root@darkstar:~# tar -zxvf broadcom-sta.tar.gz
broadcom-sta/
broadcom-sta/broadcom-sta.SlackBuild
broadcom-sta/README
broadcom-sta/doinst.sh
broadcom-sta/slack-desc
broadcom-sta/broadcom-sta.info
root@darkstar:~# ls
broadcom-sta/ broadcom-sta.tar.gz* hybrid-portsrc_x86_64-v5_100_82_38.tar.gz*
root@darkstar:~# mv hybrid-portsrc_x86_64-v5_100_82_38.tar.gz ./broadcom-sta
root@darkstar:~# cd broadcom-sta
root@darkstar:~/broadcom-sta# ./
broadcom-sta.SlackBuild hybrid-portsrc_x86_64-v5_100_82_38.tar.gz
root@darkstar:~/broadcom-sta# ./ /tmp/b
blueman-applet-0 build/
root@darkstar:~/broadcom-sta#
ok i screwed up on the blueman-applet i was trying something diff i didnt intend on that i tried b tab key and got that.lol thanks for your help
 
Old 02-25-2011, 08:52 PM   #41
colorpurple21859
Senior Member
 
Registered: Jan 2008
Location: florida
Distribution: slackware64-current, puppy, ubuntu
Posts: 1,344

Rep: Reputation: 184Reputation: 184
Quote:
root@darkstar:~/broadcom-sta# ./
This should be this
Quote:
root@darkstar:~/broadcom-sta#./broadcom-sta.Slackbuild
which will build the slack package and put it into the /tmp directory. Then this should install the package on your system:
Quote:
installpkg /tmp/broadcom-sta-5.100.82.38_2.6.29.6_smp-i486-1_SBo.tgz

Last edited by colorpurple21859; 02-25-2011 at 08:56 PM.
 
Old 02-25-2011, 09:29 PM   #42
linux/unix87
Member
 
Registered: Oct 2010
Posts: 190

Original Poster
Rep: Reputation: 6
ok i figured it out but it still doesnt work heres what i did ... oh dont pay to much attention to what i did at first i was trying to figure it out anyway here it is ok for some reason i cant copy what i did so but anyway i did install the package but i still cant get on the internet what about wicd where is the /extra at? i cant find it
 
Old 02-25-2011, 09:42 PM   #43
colorpurple21859
Senior Member
 
Registered: Jan 2008
Location: florida
Distribution: slackware64-current, puppy, ubuntu
Posts: 1,344

Rep: Reputation: 184Reputation: 184
got to slackware.com/getslack and following the links to the extra folder under the version of slackware you have installed. Download the wicd package, cd to the directory it was downloaded to and installpkg.
 
Old 02-25-2011, 09:43 PM   #44
linux/unix87
Member
 
Registered: Oct 2010
Posts: 190

Original Poster
Rep: Reputation: 6
yeah i did that but still cant get on the internet i did an iwconfig and its still showing no connection
 
Old 02-25-2011, 10:05 PM   #45
linux/unix87
Member
 
Registered: Oct 2010
Posts: 190

Original Poster
Rep: Reputation: 6
ok i got wicd installed but its not picking up any connection?
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Slackware 12.2 Wifi problem with Atheros bloodangel Linux - Newbie 5 12-26-2008 07:10 PM
Slackware 12.1 wifi connection problem. hatchetwkd Linux - Laptop and Netbook 1 09-25-2008 01:29 AM
Slackware Atheros AR5007 configuration(?) problem and Wifi issues ZeroDaHero Linux - Wireless Networking 2 08-24-2008 06:09 PM
Slackware 12.0: boot problem & sudo / wifi-radar problem War_Ensemble Slackware 7 01-15-2008 09:49 AM
Slackware Wifi Problem sc0tt Linux - Wireless Networking 5 05-06-2006 10:42 AM


All times are GMT -5. The time now is 09:05 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration