Slackware This 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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
|
 |
01-06-2006, 12:47 AM
|
#1
|
Senior Member
Registered: Sep 2004
Location: Nashville
Distribution: Manjaro, RHEL, CentOS
Posts: 2,098
Rep: 
|
Back to The basics. Newbie to Slackware
Hello Slackers. I would first like to Say Why did I not try slackware first. I love this operating system. However I am however a little confused. I am coming from Fedora Core 3
so I am not very familiar with the tarball approach to installing software.
I have seen some people do
Code:
./configure
make
make install
or I have seen the following.
Code:
./configure --prefix=/usr
make
make install
So which is the proper way to install tarballs and Where do you store the tarballs at.
If I sound confusing I appoligize it's just that as I said I am confused.
|
|
|
01-06-2006, 12:50 AM
|
#2
|
Senior Member
Registered: Dec 2004
Location: In my house.
Distribution: Ubuntu 10.10 64bit, Slackware 13.1 64-bit
Posts: 2,649
Rep:
|
You CAN do it either way. The advantage to the 'usr' prefix is that it installs under the /usr directory.
Caveat: Some programs installing from source are expecting their programs to install in specific directories. Always, always, always read the README
|
|
|
01-06-2006, 01:24 AM
|
#3
|
Member
Registered: Jul 2004
Location: [jax][fl][usa]
Distribution: Slackware64-current
Posts: 796
Rep:
|
yes... README and INSTALL are required reading.
also `./configure --help` will give you a list of
acceptable parameters.
and instead of `make install`, i recommend using
makepkg or checkinstall.
|
|
|
01-06-2006, 01:27 AM
|
#4
|
Senior Member
Registered: Dec 2004
Location: In my house.
Distribution: Ubuntu 10.10 64bit, Slackware 13.1 64-bit
Posts: 2,649
Rep:
|
DEFINATELY makepkg and chkinstall....keeps the integrity of your Slackware going
|
|
|
01-06-2006, 09:59 AM
|
#5
|
Senior Member
Registered: Sep 2004
Location: Nashville
Distribution: Manjaro, RHEL, CentOS
Posts: 2,098
Original Poster
Rep: 
|
Thanks for the quick replies.
Thanks for the quick replies. I will definetley be adding those commands to my list I am currently building. I was definetley trying to keep the integrety of Slackware.
Just one more question. Does all programs need to have the ./configure --prefix=/usr. Because most of the README files I have read just want the ./configure.
|
|
|
01-06-2006, 11:21 AM
|
#6
|
Member
Registered: Apr 2004
Location: Europe
Distribution: Debian, Slackware
Posts: 505
Rep:
|
If you don't set --prefix=/usr, the software will most likely be installed under /usr/local, that's really the only difference, both work just fine. It's more a logical division than functional. I for example prefer to keep my /usr/local for the things that don't come from slackware packages. So if I use checkinstall or makepkg to make a slack package, or use packages from linuxpackages or such, the software goes under /usr. Things installed with make install and the things I've written myself go under /usr/local.
It could also be a good idea to define --sysconfdir=/etc to have system wide configuration files fo under /etc instead of /usr/etc or /usr/local/etc. I find it easier if they are all in one place.
|
|
|
01-06-2006, 11:25 AM
|
#7
|
Member
Registered: Aug 2004
Location: Aguascalientes, AGS. Mexico.
Distribution: Slackware 13.0 kernel 2.6.29.6
Posts: 816
Rep:
|
most of the source software I've installed on Slackware just needed a
Code:
./configure && make && make install
Albeit, it is pretty important to read those readme and install files just to be sure you won't screw up 
|
|
|
01-06-2006, 11:29 AM
|
#8
|
Senior Member
Registered: Sep 2004
Location: Nashville
Distribution: Manjaro, RHEL, CentOS
Posts: 2,098
Original Poster
Rep: 
|
Thanks Aliendog. I have decided that I will probably start installing the packages like this.
Code:
./configure --prefux=/usr --sysconfdir=/etc
make
checkinstall
Unless otherwise noted by the README or INSTALL files.
|
|
|
01-06-2006, 01:41 PM
|
#9
|
Member
Registered: Feb 2004
Location: 33.31N -111.97W
Distribution: SuSE
Posts: 919
Rep:
|
Just a typo I'm sure but... --prefix, not --prefux.
|
|
|
01-06-2006, 01:50 PM
|
#10
|
Senior Member
Registered: Sep 2004
Location: Nashville
Distribution: Manjaro, RHEL, CentOS
Posts: 2,098
Original Poster
Rep: 
|
 Thanks. Brain moved faster than fingers.
|
|
|
All times are GMT -5. The time now is 08:00 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|