Refer to the manual of configure

up vote
1
down vote

favorite

I follows an instruction to install shtool

Download and extract

wget ftp://ftp.gnu.org/gnu/shtool/shtool-2.0.8.tar.gz
tar -zxvf shtool-2.0.8.tar.gz

Build the library
```
$ ./configure 
$ make
```

I could refer to make manual by

man make

How could I reach the manual about configure

edited 1 hour ago

Jeff Schaller

34.6k952115

asked 2 hours ago

Sawajiri

515

New contributor

configure is a script, not a command, thus there is no man page.
â€“Â Panther
2 hours ago

add a commentÂ |Â

up vote
1
down vote

favorite

I follows an instruction to install shtool

Download and extract

wget ftp://ftp.gnu.org/gnu/shtool/shtool-2.0.8.tar.gz
tar -zxvf shtool-2.0.8.tar.gz

Build the library
```
$ ./configure 
$ make
```

I could refer to make manual by

man make

How could I reach the manual about configure

edited 1 hour ago

Jeff Schaller

34.6k952115

asked 2 hours ago

Sawajiri

515

New contributor

configure is a script, not a command, thus there is no man page.
â€“Â Panther
2 hours ago

add a commentÂ |Â

up vote
1
down vote

favorite

I follows an instruction to install shtool

Download and extract

wget ftp://ftp.gnu.org/gnu/shtool/shtool-2.0.8.tar.gz
tar -zxvf shtool-2.0.8.tar.gz

Build the library
```
$ ./configure 
$ make
```

I could refer to make manual by

man make

How could I reach the manual about configure

edited 1 hour ago

Jeff Schaller

34.6k952115

asked 2 hours ago

Sawajiri

515

New contributor

I follows an instruction to install shtool

Download and extract

wget ftp://ftp.gnu.org/gnu/shtool/shtool-2.0.8.tar.gz
tar -zxvf shtool-2.0.8.tar.gz

Build the library
```
$ ./configure 
$ make
```

I could refer to make manual by

man make

How could I reach the manual about configure

man configure

edited 1 hour ago

Jeff Schaller

34.6k952115

asked 2 hours ago

Sawajiri

515

New contributor

edited 1 hour ago

Jeff Schaller

34.6k952115

asked 2 hours ago

Sawajiri

515

New contributor

edited 1 hour ago

Jeff Schaller

34.6k952115

edited 1 hour ago

Jeff Schaller

34.6k952115

edited 1 hour ago

Jeff Schaller

34.6k952115

asked 2 hours ago

Sawajiri

515

New contributor

asked 2 hours ago

Sawajiri

515

asked 2 hours ago

Sawajiri

515

New contributor

Sawajiri is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

configure is a script, not a command, thus there is no man page.
â€“Â Panther
2 hours ago

add a commentÂ |Â

configure is a script, not a command, thus there is no man page.
â€“Â Panther
2 hours ago

configure is a script, not a command, thus there is no man page.
â€“Â Panther
2 hours ago

add a commentÂ |Â

3 Answers
3

active

oldest

votes

up vote
2
down vote

The configure script is a script that will configure the software distribution that it was distributed with for compilation (if applicable) and installation.

These scripts are often (as in this case) created by GNU autoconf (a tool used by the developers specifically for creating portable configure scripts), which means that it will have at least a minimum of a certain set of options. One of these options is --help.

$ ./configure --help
`configure' configures this package to adapt to many kinds of systems.

Usage: ./configure [OPTION]... [VAR=VALUE]...

To assign environment variables (e.g., CC, CFLAGS...), specify them as
VAR=VALUE. See below for descriptions of some of the useful variables.

Defaults for the options are specified in brackets.

Configuration:
 -h, --help display this help and exit
 --help=short display options specific to this package
 --help=recursive display the short help of all the included packages
 -V, --version display version information and exit
 -q, --quiet, --silent do not print `checking...' messages
 --cache-file=FILE cache test results in FILE [disabled]
 -C, --config-cache alias for `--cache-file=config.cache'
 -n, --no-create do not create output files
 --srcdir=DIR find the sources in DIR [configure dir or `..']

(etc.)

There is no manual for configure as some of the available options may depend on the software that it configures (so it can't be a system-wide tool with its own manual). There is often (as in this case) both a README and an INSTALL text file distributed with the source code. These files will describe the software and how to configure it and install it. The INSTALL file will often tell you how the authors envisage the installation should happen, and you can refer to the configure --help output for how to customise this to your own needs.

edited 42 mins ago

answered 1 hour ago

Kusalananda

112k15216343

add a commentÂ |Â

up vote
1
down vote

configure is a script, not a command, thus there is no man page.

You can find information in the README file and, if the author was kind, a --help option

See https://www.linuxquestions.org/questions/linux-general-1/configure-command-315662/ or similar for a discussion.

answered 2 hours ago

Panther

80749

1

If configure was generated by autoconf, then it will always have a --help option. A README or INSTALL file may exist if the author has written and distributed them. Also, calling configure "not a command" is not quite right. It's a command like any other, it's just that it's a specific command for configuring a particular piece of software (and it's probably not located in $PATH). Any command can be a script (firefox, for example, is often a script).
â€“Â Kusalananda
1 hour ago

@Kusalananda true, but autoconf is not always used, it varies by project as does README and / or INSTALL and / or a clean or remove option(s)
â€“Â Panther
1 hour ago

1

I'd be surprised if a configure script distributed by the GNU people was not built by autoconf...
â€“Â Kusalananda
1 hour ago

add a commentÂ |Â

up vote
0
down vote

Well by ./configure command you are executing a file called configure. This is similar as executing any file so there will be no manual entry as this is not a command. While make is a command so you will find manual entry for make.

answered 2 hours ago

Debian_yadav

9323822

1

There is no distinction between "commands" and "scripts" on Unix systems.
â€“Â Kusalananda
1 hour ago

add a commentÂ |Â

Your Answer

StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);

);

Sawajiri is a new contributor. Be nice, and check out our Code of Conduct.

draft saved

draft discarded

StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f478458%2frefer-to-the-manual-of-configure%23new-answer', 'question_page');

);

Post as a guest

Name

3 Answers
3

active

oldest

votes

3 Answers
3

active

oldest

votes

up vote
2
down vote

The configure script is a script that will configure the software distribution that it was distributed with for compilation (if applicable) and installation.

$ ./configure --help
`configure' configures this package to adapt to many kinds of systems.

Usage: ./configure [OPTION]... [VAR=VALUE]...

To assign environment variables (e.g., CC, CFLAGS...), specify them as
VAR=VALUE. See below for descriptions of some of the useful variables.

Defaults for the options are specified in brackets.

Configuration:
 -h, --help display this help and exit
 --help=short display options specific to this package
 --help=recursive display the short help of all the included packages
 -V, --version display version information and exit
 -q, --quiet, --silent do not print `checking...' messages
 --cache-file=FILE cache test results in FILE [disabled]
 -C, --config-cache alias for `--cache-file=config.cache'
 -n, --no-create do not create output files
 --srcdir=DIR find the sources in DIR [configure dir or `..']

(etc.)

edited 42 mins ago

answered 1 hour ago

Kusalananda

112k15216343

add a commentÂ |Â

up vote
2
down vote

The configure script is a script that will configure the software distribution that it was distributed with for compilation (if applicable) and installation.

$ ./configure --help
`configure' configures this package to adapt to many kinds of systems.

Usage: ./configure [OPTION]... [VAR=VALUE]...

To assign environment variables (e.g., CC, CFLAGS...), specify them as
VAR=VALUE. See below for descriptions of some of the useful variables.

Defaults for the options are specified in brackets.

Configuration:
 -h, --help display this help and exit
 --help=short display options specific to this package
 --help=recursive display the short help of all the included packages
 -V, --version display version information and exit
 -q, --quiet, --silent do not print `checking...' messages
 --cache-file=FILE cache test results in FILE [disabled]
 -C, --config-cache alias for `--cache-file=config.cache'
 -n, --no-create do not create output files
 --srcdir=DIR find the sources in DIR [configure dir or `..']

(etc.)

edited 42 mins ago

answered 1 hour ago

Kusalananda

112k15216343

add a commentÂ |Â

up vote
2
down vote

The configure script is a script that will configure the software distribution that it was distributed with for compilation (if applicable) and installation.

$ ./configure --help
`configure' configures this package to adapt to many kinds of systems.

Usage: ./configure [OPTION]... [VAR=VALUE]...

To assign environment variables (e.g., CC, CFLAGS...), specify them as
VAR=VALUE. See below for descriptions of some of the useful variables.

Defaults for the options are specified in brackets.

Configuration:
 -h, --help display this help and exit
 --help=short display options specific to this package
 --help=recursive display the short help of all the included packages
 -V, --version display version information and exit
 -q, --quiet, --silent do not print `checking...' messages
 --cache-file=FILE cache test results in FILE [disabled]
 -C, --config-cache alias for `--cache-file=config.cache'
 -n, --no-create do not create output files
 --srcdir=DIR find the sources in DIR [configure dir or `..']

(etc.)

edited 42 mins ago

answered 1 hour ago

Kusalananda

112k15216343

The configure script is a script that will configure the software distribution that it was distributed with for compilation (if applicable) and installation.

$ ./configure --help
`configure' configures this package to adapt to many kinds of systems.

Usage: ./configure [OPTION]... [VAR=VALUE]...

To assign environment variables (e.g., CC, CFLAGS...), specify them as
VAR=VALUE. See below for descriptions of some of the useful variables.

Defaults for the options are specified in brackets.

Configuration:
 -h, --help display this help and exit
 --help=short display options specific to this package
 --help=recursive display the short help of all the included packages
 -V, --version display version information and exit
 -q, --quiet, --silent do not print `checking...' messages
 --cache-file=FILE cache test results in FILE [disabled]
 -C, --config-cache alias for `--cache-file=config.cache'
 -n, --no-create do not create output files
 --srcdir=DIR find the sources in DIR [configure dir or `..']

(etc.)

edited 42 mins ago

answered 1 hour ago

Kusalananda

112k15216343

edited 42 mins ago

answered 1 hour ago

Kusalananda

112k15216343

answered 1 hour ago

Kusalananda

112k15216343

answered 1 hour ago

Kusalananda

112k15216343

add a commentÂ |Â

up vote
1
down vote

configure is a script, not a command, thus there is no man page.

You can find information in the README file and, if the author was kind, a --help option

See https://www.linuxquestions.org/questions/linux-general-1/configure-command-315662/ or similar for a discussion.

answered 2 hours ago

Panther

80749

1

If configure was generated by autoconf, then it will always have a --help option. A README or INSTALL file may exist if the author has written and distributed them. Also, calling configure "not a command" is not quite right. It's a command like any other, it's just that it's a specific command for configuring a particular piece of software (and it's probably not located in $PATH). Any command can be a script (firefox, for example, is often a script).
â€“Â Kusalananda
1 hour ago

@Kusalananda true, but autoconf is not always used, it varies by project as does README and / or INSTALL and / or a clean or remove option(s)
â€“Â Panther
1 hour ago

1

I'd be surprised if a configure script distributed by the GNU people was not built by autoconf...
â€“Â Kusalananda
1 hour ago

add a commentÂ |Â

up vote
1
down vote

configure is a script, not a command, thus there is no man page.

You can find information in the README file and, if the author was kind, a --help option

See https://www.linuxquestions.org/questions/linux-general-1/configure-command-315662/ or similar for a discussion.

answered 2 hours ago

Panther

80749

1

If configure was generated by autoconf, then it will always have a --help option. A README or INSTALL file may exist if the author has written and distributed them. Also, calling configure "not a command" is not quite right. It's a command like any other, it's just that it's a specific command for configuring a particular piece of software (and it's probably not located in $PATH). Any command can be a script (firefox, for example, is often a script).
â€“Â Kusalananda
1 hour ago

@Kusalananda true, but autoconf is not always used, it varies by project as does README and / or INSTALL and / or a clean or remove option(s)
â€“Â Panther
1 hour ago

1

I'd be surprised if a configure script distributed by the GNU people was not built by autoconf...
â€“Â Kusalananda
1 hour ago

add a commentÂ |Â

up vote
1
down vote

configure is a script, not a command, thus there is no man page.

You can find information in the README file and, if the author was kind, a --help option

See https://www.linuxquestions.org/questions/linux-general-1/configure-command-315662/ or similar for a discussion.

answered 2 hours ago

Panther

80749

configure is a script, not a command, thus there is no man page.

You can find information in the README file and, if the author was kind, a --help option

See https://www.linuxquestions.org/questions/linux-general-1/configure-command-315662/ or similar for a discussion.

answered 2 hours ago

Panther

80749

answered 2 hours ago

Panther

80749

answered 2 hours ago

Panther

80749

answered 2 hours ago

Panther

80749

1

If configure was generated by autoconf, then it will always have a --help option. A README or INSTALL file may exist if the author has written and distributed them. Also, calling configure "not a command" is not quite right. It's a command like any other, it's just that it's a specific command for configuring a particular piece of software (and it's probably not located in $PATH). Any command can be a script (firefox, for example, is often a script).
â€“Â Kusalananda
1 hour ago

@Kusalananda true, but autoconf is not always used, it varies by project as does README and / or INSTALL and / or a clean or remove option(s)
â€“Â Panther
1 hour ago

1

I'd be surprised if a configure script distributed by the GNU people was not built by autoconf...
â€“Â Kusalananda
1 hour ago

add a commentÂ |Â

1

If configure was generated by autoconf, then it will always have a --help option. A README or INSTALL file may exist if the author has written and distributed them. Also, calling configure "not a command" is not quite right. It's a command like any other, it's just that it's a specific command for configuring a particular piece of software (and it's probably not located in $PATH). Any command can be a script (firefox, for example, is often a script).
â€“Â Kusalananda
1 hour ago

@Kusalananda true, but autoconf is not always used, it varies by project as does README and / or INSTALL and / or a clean or remove option(s)
â€“Â Panther
1 hour ago

1

I'd be surprised if a configure script distributed by the GNU people was not built by autoconf...
â€“Â Kusalananda
1 hour ago

If configure was generated by autoconf, then it will always have a --help option. A README or INSTALL file may exist if the author has written and distributed them. Also, calling configure "not a command" is not quite right. It's a command like any other, it's just that it's a specific command for configuring a particular piece of software (and it's probably not located in $PATH). Any command can be a script (firefox, for example, is often a script).
â€“Â Kusalananda
1 hour ago

@Kusalananda true, but autoconf is not always used, it varies by project as does README and / or INSTALL and / or a clean or remove option(s)
â€“Â Panther
1 hour ago

I'd be surprised if a configure script distributed by the GNU people was not built by autoconf...
â€“Â Kusalananda
1 hour ago

add a commentÂ |Â

up vote
0
down vote

answered 2 hours ago

Debian_yadav

9323822

1

There is no distinction between "commands" and "scripts" on Unix systems.
â€“Â Kusalananda
1 hour ago

add a commentÂ |Â

up vote
0
down vote

answered 2 hours ago

Debian_yadav

9323822

1

There is no distinction between "commands" and "scripts" on Unix systems.
â€“Â Kusalananda
1 hour ago

add a commentÂ |Â

up vote
0
down vote

answered 2 hours ago

Debian_yadav

9323822

answered 2 hours ago

Debian_yadav

9323822

answered 2 hours ago

Debian_yadav

9323822

answered 2 hours ago

Debian_yadav

9323822

answered 2 hours ago

Debian_yadav

9323822

1

There is no distinction between "commands" and "scripts" on Unix systems.
â€“Â Kusalananda
1 hour ago

add a commentÂ |Â

1

There is no distinction between "commands" and "scripts" on Unix systems.
â€“Â Kusalananda
1 hour ago

There is no distinction between "commands" and "scripts" on Unix systems.
â€“Â Kusalananda
1 hour ago

add a commentÂ |Â

Sawajiri is a new contributor. Be nice, and check out our Code of Conduct.

draft saved

draft discarded

Sawajiri is a new contributor. Be nice, and check out our Code of Conduct.

draft saved

draft discarded

Post as a guest

Name

Search This Blog

Iyfjky