Installation Instructions
*************************
-Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005,
-2006, 2007, 2008, 2009, 2010 Free Software Foundation, Inc.
+ Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005,
+2006, 2007, 2008, 2009, 2010, 2011 Free Software Foundation, Inc.
Copying and distribution of this file, with or without modification,
are permitted in any medium without royalty provided the copyright
notice and this notice are preserved. This file is offered as-is,
without warranty of any kind.
-Basic Installation
-==================
+0.1 Basic Installation
+======================
Briefly, the shell commands `./configure; make; make install' should
-configure, build, and install this package. The following
-more-detailed instructions are generic; see the `README' file for
-instructions specific to this package. Some packages provide this
-`INSTALL' file but do not implement all of the features documented
-below. The lack of an optional feature in a given package is not
-necessarily a bug. More recommendations for GNU packages can be found
-in *note Makefile Conventions: (standards)Makefile Conventions.
+configure, build, and install this package. The following more-detailed
+instructions are generic; see the `README' file for instructions
+specific to this package. Some packages provide this `INSTALL' file but
+do not implement all of the features documented below. The lack of an
+optional feature in a given package is not necessarily a bug. More
+recommendations for GNU packages can be found in *note Makefile
+Conventions: (standards)Makefile Conventions.
The `configure' shell script attempts to guess correct values for
various system-dependent variables used during compilation. It uses
file `config.log' containing compiler output (useful mainly for
debugging `configure').
- It can also use an optional file (typically called `config.cache'
-and enabled with `--cache-file=config.cache' or simply `-C') that saves
-the results of its tests to speed up reconfiguring. Caching is
-disabled by default to prevent problems with accidental use of stale
-cache files.
+ It can also use an optional file (typically called `config.cache' and
+enabled with `--cache-file=config.cache' or simply `-C') that saves the
+results of its tests to speed up reconfiguring. Caching is disabled by
+default to prevent problems with accidental use of stale cache files.
If you need to do unusual things to compile the package, please try
to figure out how `configure' could check whether to do them, and mail
The file `configure.ac' (or `configure.in') is used to create
`configure' by a program called `autoconf'. You need `configure.ac' if
-you want to change it or regenerate `configure' using a newer version
-of `autoconf'.
+you want to change it or regenerate `configure' using a newer version of
+`autoconf'.
The simplest way to compile this package is:
targets like `make install' and `make uninstall' work correctly.
This target is generally not run by end users.
-Compilers and Options
-=====================
+0.2 Compilers and Options
+=========================
Some systems require unusual options for compilation or linking that
the `configure' script does not know about. Run `./configure --help'
for details on some of the pertinent environment variables.
You can give `configure' initial values for configuration parameters
-by setting variables in the command line or in the environment. Here
-is an example:
+by setting variables in the command line or in the environment. Here is
+an example:
./configure CC=c99 CFLAGS=-g LIBS=-lposix
*Note Defining Variables::, for more details.
-Compiling For Multiple Architectures
-====================================
+0.3 Compiling For Multiple Architectures
+========================================
You can compile the package for more than one kind of computer at the
same time, by placing the object files for each architecture in their
own directory. To do this, you can use GNU `make'. `cd' to the
directory where you want the object files and executables to go and run
-the `configure' script. `configure' automatically checks for the
-source code in the directory that `configure' is in and in `..'. This
-is known as a "VPATH" build.
+the `configure' script. `configure' automatically checks for the source
+code in the directory that `configure' is in and in `..'. This is known
+as a "VPATH" build.
With a non-GNU `make', it is safer to compile the package for one
architecture at a time in the source code directory. After you have
may have to build one architecture at a time and combine the results
using the `lipo' tool if you have problems.
-Installation Names
-==================
+0.4 Installation Names
+======================
By default, `make install' installs the package's commands under
`/usr/local/bin', include files under `/usr/local/include', etc. You
In addition, if you use an unusual directory layout you can give
options like `--bindir=DIR' to specify different values for particular
kinds of files. Run `configure --help' for a list of the directories
-you can set and what kinds of files go in them. In general, the
-default for these options is expressed in terms of `${prefix}', so that
+you can set and what kinds of files go in them. In general, the default
+for these options is expressed in terms of `${prefix}', so that
specifying just `--prefix' will affect all of the other directory
specifications that were not explicitly provided.
prefix=/alternate/directory' will choose an alternate location for all
directory configuration variables that were expressed in terms of
`${prefix}'. Any directories that were specified during `configure',
-but not in terms of `${prefix}', must each be overridden at install
-time for the entire installation to be relocated. The approach of
-makefile variable overrides for each directory variable is required by
-the GNU Coding Standards, and ideally causes no recompilation.
-However, some platforms have known limitations with the semantics of
-shared libraries that end up requiring recompilation when using this
-method, particularly noticeable in packages that use GNU Libtool.
+but not in terms of `${prefix}', must each be overridden at install time
+for the entire installation to be relocated. The approach of makefile
+variable overrides for each directory variable is required by the GNU
+Coding Standards, and ideally causes no recompilation. However, some
+platforms have known limitations with the semantics of shared libraries
+that end up requiring recompilation when using this method, particularly
+noticeable in packages that use GNU Libtool.
The second method involves providing the `DESTDIR' variable. For
example, `make install DESTDIR=/alternate/directory' will prepend
when some directory options were not specified in terms of `${prefix}'
at `configure' time.
-Optional Features
-=================
+0.5 Optional Features
+=====================
If the package supports it, you can cause programs to be installed
with an extra prefix or suffix on their names by giving `configure' the
--disable-silent-rules' sets the default to verbose, which can be
overridden with `make V=0'.
-Particular systems
-==================
+0.6 Particular systems
+======================
- On HP-UX, the default C compiler is not ANSI C compatible. If GNU
-CC is not installed, it is recommended to use the following options in
+ On HP-UX, the default C compiler is not ANSI C compatible. If GNU CC
+is not installed, it is recommended to use the following options in
order to use an ANSI C compiler:
./configure CC="cc -Ae -D_XOPEN_SOURCE=500"
and if that doesn't work, install pre-built binaries of GCC for HP-UX.
On OSF/1 a.k.a. Tru64, some versions of the default C compiler cannot
-parse its `<wchar.h>' header file. The option `-nodtk' can be used as
-a workaround. If GNU CC is not installed, it is therefore recommended
-to try
+parse its `<wchar.h>' header file. The option `-nodtk' can be used as a
+workaround. If GNU CC is not installed, it is therefore recommended to
+try
./configure CC="cc"
./configure --prefix=/boot/common
-Specifying the System Type
-==========================
+0.7 Specifying the System Type
+==============================
There may be some features `configure' cannot figure out
automatically, but needs to determine by the type of machine the package
"host" platform (i.e., that on which the generated programs will
eventually be run) with `--host=TYPE'.
-Sharing Defaults
-================
+0.8 Sharing Defaults
+====================
If you want to set default values for `configure' scripts to share,
you can create a site shell script called `config.site' that gives
`CONFIG_SITE' environment variable to the location of the site script.
A warning: not all `configure' scripts look for a site script.
-Defining Variables
-==================
+0.9 Defining Variables
+======================
Variables not defined in a site shell script can be set in the
environment passed to `configure'. However, some packages may run
causes the specified `gcc' to be used as the C compiler (unless it is
overridden in the site shell script).
-Unfortunately, this technique does not work for `CONFIG_SHELL' due to
-an Autoconf bug. Until the bug is fixed you can use this workaround:
+Unfortunately, this technique does not work for `CONFIG_SHELL' due to an
+Autoconf bug. Until the bug is fixed you can use this workaround:
CONFIG_SHELL=/bin/bash /bin/bash ./configure CONFIG_SHELL=/bin/bash
-`configure' Invocation
-======================
+0.10 `configure' Invocation
+===========================
`configure' recognizes the following options to control how it
operates.
`--help=short'
`--help=recursive'
Print a summary of the options unique to this package's
- `configure', and exit. The `short' variant lists options used
- only in the top level, while the `recursive' variant lists options
- also present in any nested packages.
+ `configure', and exit. The `short' variant lists options used only
+ in the top level, while the `recursive' variant lists options also
+ present in any nested packages.
`--version'
`-V'
`configure' can determine that directory automatically.
`--prefix=DIR'
- Use DIR as the installation prefix. *note Installation Names::
- for more details, including other options available for fine-tuning
- the installation locations.
+ Use DIR as the installation prefix. *note Installation Names:: for
+ more details, including other options available for fine-tuning the
+ installation locations.
`--no-create'
`-n'
Installation Instructions
*************************
-Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005,
-2006, 2007, 2008, 2009, 2010 Free Software Foundation, Inc.
+ Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005,
+2006, 2007, 2008, 2009, 2010, 2011 Free Software Foundation, Inc.
Copying and distribution of this file, with or without modification,
are permitted in any medium without royalty provided the copyright
notice and this notice are preserved. This file is offered as-is,
without warranty of any kind.
-Basic Installation
-==================
+0.1 Basic Installation
+======================
Briefly, the shell commands './configure; make; make install' should
-configure, build, and install this package. The following
-more-detailed instructions are generic; see the 'README' file for
-instructions specific to this package. Some packages provide this
-'INSTALL' file but do not implement all of the features documented
-below. The lack of an optional feature in a given package is not
-necessarily a bug. More recommendations for GNU packages can be found
-in *note Makefile Conventions: (standards)Makefile Conventions.
+configure, build, and install this package. The following more-detailed
+instructions are generic; see the 'README' file for instructions
+specific to this package. Some packages provide this 'INSTALL' file but
+do not implement all of the features documented below. The lack of an
+optional feature in a given package is not necessarily a bug. More
+recommendations for GNU packages can be found in *note Makefile
+Conventions: (standards)Makefile Conventions.
The 'configure' shell script attempts to guess correct values for
various system-dependent variables used during compilation. It uses
file 'config.log' containing compiler output (useful mainly for
debugging 'configure').
- It can also use an optional file (typically called 'config.cache'
-and enabled with '--cache-file=config.cache' or simply '-C') that saves
-the results of its tests to speed up reconfiguring. Caching is
-disabled by default to prevent problems with accidental use of stale
-cache files.
+ It can also use an optional file (typically called 'config.cache' and
+enabled with '--cache-file=config.cache' or simply '-C') that saves the
+results of its tests to speed up reconfiguring. Caching is disabled by
+default to prevent problems with accidental use of stale cache files.
If you need to do unusual things to compile the package, please try
to figure out how 'configure' could check whether to do them, and mail
The file 'configure.ac' (or 'configure.in') is used to create
'configure' by a program called 'autoconf'. You need 'configure.ac' if
-you want to change it or regenerate 'configure' using a newer version
-of 'autoconf'.
+you want to change it or regenerate 'configure' using a newer version of
+'autoconf'.
The simplest way to compile this package is:
targets like 'make install' and 'make uninstall' work correctly.
This target is generally not run by end users.
-Compilers and Options
-=====================
+0.2 Compilers and Options
+=========================
Some systems require unusual options for compilation or linking that
the 'configure' script does not know about. Run './configure --help'
for details on some of the pertinent environment variables.
You can give 'configure' initial values for configuration parameters
-by setting variables in the command line or in the environment. Here
-is an example:
+by setting variables in the command line or in the environment. Here is
+an example:
./configure CC=c99 CFLAGS=-g LIBS=-lposix
*Note Defining Variables::, for more details.
-Compiling For Multiple Architectures
-====================================
+0.3 Compiling For Multiple Architectures
+========================================
You can compile the package for more than one kind of computer at the
same time, by placing the object files for each architecture in their
own directory. To do this, you can use GNU 'make'. 'cd' to the
directory where you want the object files and executables to go and run
-the 'configure' script. 'configure' automatically checks for the
-source code in the directory that 'configure' is in and in '..'. This
-is known as a "VPATH" build.
+the 'configure' script. 'configure' automatically checks for the source
+code in the directory that 'configure' is in and in '..'. This is known
+as a "VPATH" build.
With a non-GNU 'make', it is safer to compile the package for one
architecture at a time in the source code directory. After you have
may have to build one architecture at a time and combine the results
using the 'lipo' tool if you have problems.
-Installation Names
-==================
+0.4 Installation Names
+======================
By default, 'make install' installs the package's commands under
'/usr/local/bin', include files under '/usr/local/include', etc. You
In addition, if you use an unusual directory layout you can give
options like '--bindir=DIR' to specify different values for particular
kinds of files. Run 'configure --help' for a list of the directories
-you can set and what kinds of files go in them. In general, the
-default for these options is expressed in terms of '${prefix}', so that
+you can set and what kinds of files go in them. In general, the default
+for these options is expressed in terms of '${prefix}', so that
specifying just '--prefix' will affect all of the other directory
specifications that were not explicitly provided.
prefix=/alternate/directory' will choose an alternate location for all
directory configuration variables that were expressed in terms of
'${prefix}'. Any directories that were specified during 'configure',
-but not in terms of '${prefix}', must each be overridden at install
-time for the entire installation to be relocated. The approach of
-makefile variable overrides for each directory variable is required by
-the GNU Coding Standards, and ideally causes no recompilation.
-However, some platforms have known limitations with the semantics of
-shared libraries that end up requiring recompilation when using this
-method, particularly noticeable in packages that use GNU Libtool.
+but not in terms of '${prefix}', must each be overridden at install time
+for the entire installation to be relocated. The approach of makefile
+variable overrides for each directory variable is required by the GNU
+Coding Standards, and ideally causes no recompilation. However, some
+platforms have known limitations with the semantics of shared libraries
+that end up requiring recompilation when using this method, particularly
+noticeable in packages that use GNU Libtool.
The second method involves providing the 'DESTDIR' variable. For
example, 'make install DESTDIR=/alternate/directory' will prepend
when some directory options were not specified in terms of '${prefix}'
at 'configure' time.
-Optional Features
-=================
+0.5 Optional Features
+=====================
If the package supports it, you can cause programs to be installed
with an extra prefix or suffix on their names by giving 'configure' the
--disable-silent-rules' sets the default to verbose, which can be
overridden with 'make V=0'.
-Particular systems
-==================
+0.6 Particular systems
+======================
- On HP-UX, the default C compiler is not ANSI C compatible. If GNU
-CC is not installed, it is recommended to use the following options in
+ On HP-UX, the default C compiler is not ANSI C compatible. If GNU CC
+is not installed, it is recommended to use the following options in
order to use an ANSI C compiler:
./configure CC="cc -Ae -D_XOPEN_SOURCE=500"
and if that doesn't work, install pre-built binaries of GCC for HP-UX.
On OSF/1 a.k.a. Tru64, some versions of the default C compiler cannot
-parse its '<wchar.h>' header file. The option '-nodtk' can be used as
-a workaround. If GNU CC is not installed, it is therefore recommended
-to try
+parse its '<wchar.h>' header file. The option '-nodtk' can be used as a
+workaround. If GNU CC is not installed, it is therefore recommended to
+try
./configure CC="cc"
./configure --prefix=/boot/common
-Specifying the System Type
-==========================
+0.7 Specifying the System Type
+==============================
There may be some features 'configure' cannot figure out
automatically, but needs to determine by the type of machine the package
"host" platform (i.e., that on which the generated programs will
eventually be run) with '--host=TYPE'.
-Sharing Defaults
-================
+0.8 Sharing Defaults
+====================
If you want to set default values for 'configure' scripts to share,
you can create a site shell script called 'config.site' that gives
'CONFIG_SITE' environment variable to the location of the site script.
A warning: not all 'configure' scripts look for a site script.
-Defining Variables
-==================
+0.9 Defining Variables
+======================
Variables not defined in a site shell script can be set in the
environment passed to 'configure'. However, some packages may run
causes the specified 'gcc' to be used as the C compiler (unless it is
overridden in the site shell script).
-Unfortunately, this technique does not work for 'CONFIG_SHELL' due to
-an Autoconf bug. Until the bug is fixed you can use this workaround:
+Unfortunately, this technique does not work for 'CONFIG_SHELL' due to an
+Autoconf bug. Until the bug is fixed you can use this workaround:
CONFIG_SHELL=/bin/bash /bin/bash ./configure CONFIG_SHELL=/bin/bash
-'configure' Invocation
-======================
+0.10 'configure' Invocation
+===========================
'configure' recognizes the following options to control how it
operates.
'--help=short'
'--help=recursive'
Print a summary of the options unique to this package's
- 'configure', and exit. The 'short' variant lists options used
- only in the top level, while the 'recursive' variant lists options
- also present in any nested packages.
+ 'configure', and exit. The 'short' variant lists options used only
+ in the top level, while the 'recursive' variant lists options also
+ present in any nested packages.
'--version'
'-V'
'configure' can determine that directory automatically.
'--prefix=DIR'
- Use DIR as the installation prefix. *note Installation Names::
- for more details, including other options available for fine-tuning
- the installation locations.
+ Use DIR as the installation prefix. *note Installation Names:: for
+ more details, including other options available for fine-tuning the
+ installation locations.
'--no-create'
'-n'
Installation Instructions
*************************
-Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005,
-2006, 2007, 2008, 2009, 2010 Free Software Foundation, Inc.
+ Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005,
+2006, 2007, 2008, 2009, 2010, 2011 Free Software Foundation, Inc.
Copying and distribution of this file, with or without modification,
are permitted in any medium without royalty provided the copyright
notice and this notice are preserved. This file is offered as-is,
without warranty of any kind.
-Basic Installation
-==================
+0.1 Basic Installation
+======================
Briefly, the shell commands ‘./configure; make; make install’ should
-configure, build, and install this package. The following
-more-detailed instructions are generic; see the ‘README’ file for
-instructions specific to this package. Some packages provide this
-‘INSTALL’ file but do not implement all of the features documented
-below. The lack of an optional feature in a given package is not
-necessarily a bug. More recommendations for GNU packages can be found
-in *note Makefile Conventions: (standards)Makefile Conventions.
+configure, build, and install this package. The following more-detailed
+instructions are generic; see the ‘README’ file for instructions
+specific to this package. Some packages provide this ‘INSTALL’ file but
+do not implement all of the features documented below. The lack of an
+optional feature in a given package is not necessarily a bug. More
+recommendations for GNU packages can be found in *note Makefile
+Conventions: (standards)Makefile Conventions.
The ‘configure’ shell script attempts to guess correct values for
various system-dependent variables used during compilation. It uses
file ‘config.log’ containing compiler output (useful mainly for
debugging ‘configure’).
- It can also use an optional file (typically called ‘config.cache’
-and enabled with ‘--cache-file=config.cache’ or simply ‘-C’) that saves
-the results of its tests to speed up reconfiguring. Caching is
-disabled by default to prevent problems with accidental use of stale
-cache files.
+ It can also use an optional file (typically called ‘config.cache’ and
+enabled with ‘--cache-file=config.cache’ or simply ‘-C’) that saves the
+results of its tests to speed up reconfiguring. Caching is disabled by
+default to prevent problems with accidental use of stale cache files.
If you need to do unusual things to compile the package, please try
to figure out how ‘configure’ could check whether to do them, and mail
The file ‘configure.ac’ (or ‘configure.in’) is used to create
‘configure’ by a program called ‘autoconf’. You need ‘configure.ac’ if
-you want to change it or regenerate ‘configure’ using a newer version
-of ‘autoconf’.
+you want to change it or regenerate ‘configure’ using a newer version of
+‘autoconf’.
The simplest way to compile this package is:
targets like ‘make install’ and ‘make uninstall’ work correctly.
This target is generally not run by end users.
-Compilers and Options
-=====================
+0.2 Compilers and Options
+=========================
Some systems require unusual options for compilation or linking that
the ‘configure’ script does not know about. Run ‘./configure --help’
for details on some of the pertinent environment variables.
You can give ‘configure’ initial values for configuration parameters
-by setting variables in the command line or in the environment. Here
-is an example:
+by setting variables in the command line or in the environment. Here is
+an example:
./configure CC=c99 CFLAGS=-g LIBS=-lposix
*Note Defining Variables::, for more details.
-Compiling For Multiple Architectures
-====================================
+0.3 Compiling For Multiple Architectures
+========================================
You can compile the package for more than one kind of computer at the
same time, by placing the object files for each architecture in their
own directory. To do this, you can use GNU ‘make’. ‘cd’ to the
directory where you want the object files and executables to go and run
-the ‘configure’ script. ‘configure’ automatically checks for the
-source code in the directory that ‘configure’ is in and in ‘..’. This
-is known as a "VPATH" build.
+the ‘configure’ script. ‘configure’ automatically checks for the source
+code in the directory that ‘configure’ is in and in ‘..’. This is known
+as a "VPATH" build.
With a non-GNU ‘make’, it is safer to compile the package for one
architecture at a time in the source code directory. After you have
may have to build one architecture at a time and combine the results
using the ‘lipo’ tool if you have problems.
-Installation Names
-==================
+0.4 Installation Names
+======================
By default, ‘make install’ installs the package's commands under
‘/usr/local/bin’, include files under ‘/usr/local/include’, etc. You
In addition, if you use an unusual directory layout you can give
options like ‘--bindir=DIR’ to specify different values for particular
kinds of files. Run ‘configure --help’ for a list of the directories
-you can set and what kinds of files go in them. In general, the
-default for these options is expressed in terms of ‘${prefix}’, so that
+you can set and what kinds of files go in them. In general, the default
+for these options is expressed in terms of ‘${prefix}’, so that
specifying just ‘--prefix’ will affect all of the other directory
specifications that were not explicitly provided.
prefix=/alternate/directory' will choose an alternate location for all
directory configuration variables that were expressed in terms of
‘${prefix}’. Any directories that were specified during ‘configure’,
-but not in terms of ‘${prefix}’, must each be overridden at install
-time for the entire installation to be relocated. The approach of
-makefile variable overrides for each directory variable is required by
-the GNU Coding Standards, and ideally causes no recompilation.
-However, some platforms have known limitations with the semantics of
-shared libraries that end up requiring recompilation when using this
-method, particularly noticeable in packages that use GNU Libtool.
+but not in terms of ‘${prefix}’, must each be overridden at install time
+for the entire installation to be relocated. The approach of makefile
+variable overrides for each directory variable is required by the GNU
+Coding Standards, and ideally causes no recompilation. However, some
+platforms have known limitations with the semantics of shared libraries
+that end up requiring recompilation when using this method, particularly
+noticeable in packages that use GNU Libtool.
The second method involves providing the ‘DESTDIR’ variable. For
example, ‘make install DESTDIR=/alternate/directory’ will prepend
when some directory options were not specified in terms of ‘${prefix}’
at ‘configure’ time.
-Optional Features
-=================
+0.5 Optional Features
+=====================
If the package supports it, you can cause programs to be installed
with an extra prefix or suffix on their names by giving ‘configure’ the
--disable-silent-rules' sets the default to verbose, which can be
overridden with ‘make V=0’.
-Particular systems
-==================
+0.6 Particular systems
+======================
- On HP-UX, the default C compiler is not ANSI C compatible. If GNU
-CC is not installed, it is recommended to use the following options in
+ On HP-UX, the default C compiler is not ANSI C compatible. If GNU CC
+is not installed, it is recommended to use the following options in
order to use an ANSI C compiler:
./configure CC="cc -Ae -D_XOPEN_SOURCE=500"
and if that doesn't work, install pre-built binaries of GCC for HP-UX.
On OSF/1 a.k.a. Tru64, some versions of the default C compiler cannot
-parse its ‘<wchar.h>’ header file. The option ‘-nodtk’ can be used as
-a workaround. If GNU CC is not installed, it is therefore recommended
-to try
+parse its ‘<wchar.h>’ header file. The option ‘-nodtk’ can be used as a
+workaround. If GNU CC is not installed, it is therefore recommended to
+try
./configure CC="cc"
./configure --prefix=/boot/common
-Specifying the System Type
-==========================
+0.7 Specifying the System Type
+==============================
There may be some features ‘configure’ cannot figure out
automatically, but needs to determine by the type of machine the package
"host" platform (i.e., that on which the generated programs will
eventually be run) with ‘--host=TYPE’.
-Sharing Defaults
-================
+0.8 Sharing Defaults
+====================
If you want to set default values for ‘configure’ scripts to share,
you can create a site shell script called ‘config.site’ that gives
‘CONFIG_SITE’ environment variable to the location of the site script.
A warning: not all ‘configure’ scripts look for a site script.
-Defining Variables
-==================
+0.9 Defining Variables
+======================
Variables not defined in a site shell script can be set in the
environment passed to ‘configure’. However, some packages may run
causes the specified ‘gcc’ to be used as the C compiler (unless it is
overridden in the site shell script).
-Unfortunately, this technique does not work for ‘CONFIG_SHELL’ due to
-an Autoconf bug. Until the bug is fixed you can use this workaround:
+Unfortunately, this technique does not work for ‘CONFIG_SHELL’ due to an
+Autoconf bug. Until the bug is fixed you can use this workaround:
CONFIG_SHELL=/bin/bash /bin/bash ./configure CONFIG_SHELL=/bin/bash
-‘configure’ Invocation
-======================
+0.10 ‘configure’ Invocation
+===========================
‘configure’ recognizes the following options to control how it
operates.
‘--help=short’
‘--help=recursive’
Print a summary of the options unique to this package's
- ‘configure’, and exit. The ‘short’ variant lists options used
- only in the top level, while the ‘recursive’ variant lists options
- also present in any nested packages.
+ ‘configure’, and exit. The ‘short’ variant lists options used only
+ in the top level, while the ‘recursive’ variant lists options also
+ present in any nested packages.
‘--version’
‘-V’
‘configure’ can determine that directory automatically.
‘--prefix=DIR’
- Use DIR as the installation prefix. *note Installation Names::
- for more details, including other options available for fine-tuning
- the installation locations.
+ Use DIR as the installation prefix. *note Installation Names:: for
+ more details, including other options available for fine-tuning the
+ installation locations.
‘--no-create’
‘-n’
projects / pspp / commitdiff