Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Yeah, I'm STILL new to Linux, and I STILL don't know how to do a library of things.
I've noticed that almost all the software I download states that it must be compiled, and it gives me strange instructions.
How do I do that, and why can't I just get these programs already compiled?
If you're using SuSE, you generally can - you want rpms (packages ending in .rpm) built for SuSE. To compile you need gcc and host of other applications that may not be installed by default with SuSE (not familiar with SuSE). Then, since you've read the instructions, you just follow them. Ideally, with standard tarballs (*.tar.gz, *.tar.bz2, and so on), it's
./configure (check out what's where on your system)
make (translate the source code to binaries)
make install (put the stuff where it belongs)
There's a guide on compiling somewhere around here but I haven't been able to find it lately. If you find it, it'll go into details.
You will need to su to root just before you do the 'make install' step. Most programs will install the binary in either /usr/bin or /usr/local/bin. There may be library files installed in /usr/lib also. To write to these directories, you have to be the root user.
Yeah, thanks for catching that. With root stuff I tend to think of 'su' as understood, but it's not 'understood' if you don't know it.
If you install something to a directory you do have write permission to, say ~/bin, after compiling with the --prefix flag, you won't need to su but that's not usual procedure. Like jschiwal says, mostly its system directories and you won't have permission to those.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.