Configure script: Difference between revisions

Content deleted Content added
Monkbot (talk | contribs)
m Task 18 (cosmetic): eval 3 templates: hyphenate params (3×);
Usage: corrected the explanation concerning specifying the executable's ___location. Explanation of my correction: having to specify the executable's ___location is a recommended practice. It is implemented in the configuration, as shipped. The previous wording made it seem hardcoded in the OS executables. Specifying the ___location doesn't require an absolute path -- a relative path suffices.
Line 14:
</syntaxhighlight>
 
One must type <code>./configure</code> rather than simply <code>configure</code> to indicate to the shell that the script is in the current directory. By defaultThis is because, foras a security reasonsprecaution, [[Unix]] operatingconfigurations systems do notdon't search the current directory for executables. so oneSo, mustto giveexecute theprograms fullin paththat explicitlydirectory, toone must explicitly avoidspecify antheir error___location.<ref>{{cite web |url=http://www.control-escape.com/linux/lx-swinstall-tar.html |title=Compiling Linux Software from Source Code |publisher=Control-Escape's Linux Help Engine |access-date=20 November 2010}}</ref>
 
Upon its completion, <code>configure</code> prints a report to <code>config.log</code>. Running <code>./configure --help</code> gives a list of command line arguments, for enabling or disabling additional features such as: