user-avatar
Today is Friday
March 13, 2026

Archives: 4 October 2009

October 4, 2009

Understanding software installation in linux, configure, make, make install

by viggy — Categories: Uncategorized — Tags: , , , Leave a comment

Courtsey:: http://www.codecoffee.com/tipsforlinux/articles/27.html

Each software comes with a few files which are solely for the purpose of installation sake. One of them is the configure script. The user has to run the following command at the prompt

$ ./configure

The above command makes the shell run the script named ‘ configure ‘ which exists in the current directory. The configure script basically consists of many lines which are used to check some details about the machine on which the software is going to be installed. This script checks for lots of dependencies on your system. For the particular software to work properly, it may be requiring a lot of things to be existing on your machine already. When you run the configure script you would see a lot of output on the screen , each being some sort of question and a respective yes/no as the reply. If any of the major requirements are missing on your system, the configure script would exit and you cannot proceed with the installation, until you get those required things.

The main job of the configure script is to create a ‘ Makefile ‘ . This is a very important file for the installation process. Depending on the results of the tests (checks) that the configure script performed it would write down the various steps that need to be taken (while compiling the software) in the file named Makefile.

If you get no errors and the configure script runs successfully (if there is any error the last few lines of the output would glaringly be stating the error) then you can proceed with the next command which is

$ make

‘ make ‘ is actually a utility which exists on almost all Unix systems. For make utility to work it requires a file named Makefile in the same directory in which you run make. As we have seen the configure script’s main job was to create a file named Makefile to be used with make utility. (Sometimes the Makefile is named as makefile also)

make would use the directions present in the Makefile and proceed with the installation. The Makefile indicates the sequence, that Linux must follow to build various components / sub-programs of your software. The sequence depends on the way the software is designed as well as many other factors.

The Makefile actually has a lot of labels (sort of names for different sections). Hence depending on what needs to be done the control would be passed to the different sections within the Makefile Or it is possible that at the end of one of the section there is a command to go to some next section.

Basically the make utility compiles all your program code and creates the executables. For particular section of the program to complete might require some other part of the code already ready, this is what the Makefile does. It sets the sequence for the events so that your program does not complain about missing dependencies.

One of the labels present in the Makefile happens to be named ‘ install ‘ .

If make ran successfully then you are almost done with the installation. Only the last step remains which is

$ make install

As indicated before make uses the file named Makefile in the same directory. When you run make without any parameters, the instruction in the Makefile begin executing from the start and as per the rules defined within the Makefile (particular sections of the code may execute after one another..thats why labels are used..to jump from one section to another). But when you run make with install as the parameter, the make utility searches for a label named install within the Makefile, and executes only that section of the Makefile.

The install section happens to be only a part where the executables and other required files created during the last step (i.e. make) are copied into the required final directories on your machine. E.g. the executable that the user runs may be copied to the /usr/local/bin so that all users are able to run the software. Similarly all the other files are also copied to the standard directories in Linux. Remember that when you ran make, all the executables were created in the temporary directory where you had unzipped your original tarball. So when you run make install, these executables are copied to the final directories.

Thats it !! Now the installation process must be clear to you. You surely will feel more at home when you begin your next software installation.

October 4, 2009

how to download an ftp link from browser

by viggy — Categories: Uncategorized — Tags: , , , Leave a comment

Let me first describe what was the problem faced by me?

I was in my friend’s laptop and ssh-ed in my system. Now i wanted to download a tar file from internet to my system. The link mentioned was a ftp link. When i tried to use wget, I got a permissioned denied error. So I was left with 2 options, either to download it in my friend’s lappy and then scp it into my system or download it using link2 console WWW browser. I chose the later even though it was my first time to try that.

First after starting links2 in console, using links2 command, we need to open the link where the download link is present. For that, the shortcut-key to get address bar is “g”. (Note that I first tried to directly open the ftp link assuming that it would directly download the file, but instead I came to know that links2 actaully tries to open that as a page and hence file does not get downloaded, hence no use). Now after you have entered the web-page, go to the download link. Now you can download the file by using the shorcut-key “d”. It gives you an option to rename the file that is being downloaded. After you have given it a suitable name, you are ready to download it. Note that the file is downloaded in the present working directory(the directory from where you executed the links2 command).
Also let me mention here that “esc” is the key to get the toolbar in links2 browser.