how do I go about to install the ./configure the my computer states found or directory not found

Asked by TRILEY83

I thought whenever you needed to compress or decompress a file this command was needed but my computer states file or directory not found relating to the command ./CONFIGURE is it not true this command is important also in getting or installing another kernel .

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Solved by:
W. Prins
Solved:
Last query:
Last reply:
Revision history for this message
TRILEY83 (triley1983) said :
#1

I'm having trouble with this command: ./configure because my computer gives an error message file or directory not found. I thought this was a very important configuration file or command such as ./configure, make, makefile, install make, make clean. But why is this important file not install into my system and how do I go about install this so I can either complie a new kernel or compress or decompress files.

Revision history for this message
Best W. Prins (wprins) said :
#2

When you issue a command, e.g. say "gzip file.dat", the system will look for the command "gzip" in all the folders specified in the path. If you however explicitly specify a path, for example "/etc/gzip file.dat" then the system will assume you know what you're doing and will look for gzip in the folder "/etc". If it's not found there, it will complain and say that it could not find the file/command. Now, "./configure" is actually a command of the latter form, the directory you're specifying is "./", which is the *current* folder, and the command is "configure". So, firstly, if you're not in the folder where "configure" resides, then you will obviously get that error message. Secondly, as you might guess from that, "configure" is not a "standard" command that is supposed to be installed on your system, but is rather a script name used as "standard" for source distributions on Unix, which when run, will set up the make files and so on for compiling on the particular flavour of Unix/Linux you're running.

The bottom line: You ran the command from the wrong folder. Make sure you do "cd sourcefolder" first (where you obviously must insert whatever the proper folder name is where you've put the project source code into "sourcefolder"), and then check that you can see the "configure" script there with "ls -al". Then run it with "./configure"

Revision history for this message
TRILEY83 (triley1983) said :
#3

Thanks ByteJuggler, that solved my question.