5c5
< 2006 Free Software Foundation, Inc.
---
> 2006, 2007, 2008, 2009 Free Software Foundation, Inc.
7,8c7,10
< This file is free documentation; the Free Software Foundation gives
< unlimited permission to copy, distribute and modify it.
---
> 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.
13c15
< Briefly, the shell commands `./configure; make; make install' should
---
> Briefly, the shell commands `./configure; make; make install' should
16c18,22
< instructions specific to this package.
---
> 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.
45c51
< The simplest way to compile this package is:
---
> The simplest way to compile this package is:
56c62
< the package.
---
> the package, generally using the just-built uninstalled binaries.
59c65,68
< documentation.
---
> documentation. When installing into a prefix owned by root, it is
> recommended that the package be configured and built as a regular
> user, and only the `make install' phase executed with root
> privileges.
61c70,77
< 5. You can remove the program binaries and object files from the
---
> 5. Optionally, type `make installcheck' to repeat any self-tests, but
> this time using the binaries in their final installed location.
> This target does not install anything. Running this target as a
> regular user, particularly if the prior `make install' required
> root privileges, verifies that the installation completed
> correctly.
>
> 6. You can remove the program binaries and object files from the
69a86,95
> 7. Often, you can also type `make uninstall' to remove the installed
> files again. In practice, not all packages have tested that
> uninstallation works correctly, even though it is required by the
> GNU Coding Standards.
>
> 8. Some packages, particularly those that use Automake, provide `make
> distcheck', which can by used by developers to test that all other
> targets like `make install' and `make uninstall' work correctly.
> This target is generally not run by end users.
>
73,75c99,101
< 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.
---
> 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.
88c114
< You can compile the package for more than one kind of computer at the
---
> You can compile the package for more than one kind of computer at the
93c119,120
< source code in the directory that `configure' is in and in `..'.
---
> source code in the directory that `configure' is in and in `..'. This
> is known as a "VPATH" build.
99a127,140
> On MacOS X 10.5 and later systems, you can create libraries and
> executables that work on multiple system types--known as "fat" or
> "universal" binaries--by specifying multiple `-arch' options to the
> compiler but only a single `-arch' option to the preprocessor. Like
> this:
>
> ./configure CC="gcc -arch i386 -arch x86_64 -arch ppc -arch ppc64" \
> CXX="g++ -arch i386 -arch x86_64 -arch ppc -arch ppc64" \
> CPP="gcc -E" CXXCPP="g++ -E"
>
> This is not guaranteed to produce working output in all cases, you
> may have to build one architecture at a time and combine the results
> using the `lipo' tool if you have problems.
>
103c144
< By default, `make install' installs the package's commands under
---
> By default, `make install' installs the package's commands under
106c147,148
< `configure' the option `--prefix=PREFIX'.
---
> `configure' the option `--prefix=PREFIX', where PREFIX must be an
> absolute file name.
117c159,162
< you can set and what kinds of files go in them.
---
> 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.
119,121c164,168
< 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
< option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
---
> The most portable way to affect installation locations is to pass the
> correct locations to `configure'; however, many packages provide one or
> both of the following shortcuts of passing variable assignments to the
> `make install' command line to change installation locations without
> having to reconfigure or recompile.
122a170,191
> The first method involves providing an override variable for each
> affected directory. For example, `make install
> 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.
>
> The second method involves providing the `DESTDIR' variable. For
> example, `make install DESTDIR=/alternate/directory' will prepend
> `/alternate/directory' before all installation names. The approach of
> `DESTDIR' overrides is not required by the GNU Coding Standards, and
> does not work on platforms that have drive letters. On the other hand,
> it does better at avoiding recompilation issues, and works well even
> when some directory options were not specified in terms of `${prefix}'
> at `configure' time.
>
126c195,199
< Some packages pay attention to `--enable-FEATURE' options to
---
> 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
> option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
>
> Some packages pay attention to `--enable-FEATURE' options to
137a211,249
> Some packages offer the ability to configure how verbose the
> execution of `make' will be. For these packages, running `./configure
> --enable-silent-rules' sets the default to minimal output, which can be
> overridden with `make V=1'; while running `./configure
> --disable-silent-rules' sets the default to verbose, which can be
> overridden with `make V=0'.
>
> 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
> 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
>
> ./configure CC="cc"
>
> and if that doesn't work, try
>
> ./configure CC="cc -nodtk"
>
> On Solaris, don't put `/usr/ucb' early in your `PATH'. This
> directory contains several dysfunctional programs; working variants of
> these programs are available in `/usr/bin'. So, if you need `/usr/ucb'
> in your `PATH', put it _after_ `/usr/bin'.
>
> On Haiku, software installed for all users goes in `/boot/common',
> not `/usr/local'. It is recommended to use the following options:
>
> ./configure --prefix=/boot/common
>
141,145c253,257
< There may be some features `configure' cannot figure out automatically,
< but needs to determine by the type of machine the package will run on.
< Usually, assuming the package is built to be run on the _same_
< architectures, `configure' can figure that out, but if it prints a
< message saying it cannot guess the machine type, give it the
---
> There may be some features `configure' cannot figure out
> automatically, but needs to determine by the type of machine the package
> will run on. Usually, assuming the package is built to be run on the
> _same_ architectures, `configure' can figure that out, but if it prints
> a message saying it cannot guess the machine type, give it the
153c265,266
< OS KERNEL-OS
---
> OS
> KERNEL-OS
171,173c284,286
< If you want to set default values for `configure' scripts to share, you
< can create a site shell script called `config.site' that gives default
< values for variables like `CC', `cache_file', and `prefix'.
---
> If you want to set default values for `configure' scripts to share,
> you can create a site shell script called `config.site' that gives
> default values for variables like `CC', `cache_file', and `prefix'.
182c295
< Variables not defined in a site shell script can be set in the
---
> Variables not defined in a site shell script can be set in the
201c314,315
< `configure' recognizes the following options to control how it operates.
---
> `configure' recognizes the following options to control how it
> operates.
205c319
< Print a summary of the options to `configure', and exit.
---
> Print a summary of all of the options to `configure', and exit.
206a321,327
> `--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.
>
231a353,362
> `--prefix=DIR'
> 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'
> Run the configure checks, but stop before creating any output
> files.
>
< 2006 Free Software Foundation, Inc.
---
> 2006, 2007, 2008, 2009 Free Software Foundation, Inc.
7,8c7,10
< This file is free documentation; the Free Software Foundation gives
< unlimited permission to copy, distribute and modify it.
---
> 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.
13c15
< Briefly, the shell commands `./configure; make; make install' should
---
> Briefly, the shell commands `./configure; make; make install' should
16c18,22
< instructions specific to this package.
---
> 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.
45c51
< The simplest way to compile this package is:
---
> The simplest way to compile this package is:
56c62
< the package.
---
> the package, generally using the just-built uninstalled binaries.
59c65,68
< documentation.
---
> documentation. When installing into a prefix owned by root, it is
> recommended that the package be configured and built as a regular
> user, and only the `make install' phase executed with root
> privileges.
61c70,77
< 5. You can remove the program binaries and object files from the
---
> 5. Optionally, type `make installcheck' to repeat any self-tests, but
> this time using the binaries in their final installed location.
> This target does not install anything. Running this target as a
> regular user, particularly if the prior `make install' required
> root privileges, verifies that the installation completed
> correctly.
>
> 6. You can remove the program binaries and object files from the
69a86,95
> 7. Often, you can also type `make uninstall' to remove the installed
> files again. In practice, not all packages have tested that
> uninstallation works correctly, even though it is required by the
> GNU Coding Standards.
>
> 8. Some packages, particularly those that use Automake, provide `make
> distcheck', which can by used by developers to test that all other
> targets like `make install' and `make uninstall' work correctly.
> This target is generally not run by end users.
>
73,75c99,101
< 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.
---
> 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.
88c114
< You can compile the package for more than one kind of computer at the
---
> You can compile the package for more than one kind of computer at the
93c119,120
< source code in the directory that `configure' is in and in `..'.
---
> source code in the directory that `configure' is in and in `..'. This
> is known as a "VPATH" build.
99a127,140
> On MacOS X 10.5 and later systems, you can create libraries and
> executables that work on multiple system types--known as "fat" or
> "universal" binaries--by specifying multiple `-arch' options to the
> compiler but only a single `-arch' option to the preprocessor. Like
> this:
>
> ./configure CC="gcc -arch i386 -arch x86_64 -arch ppc -arch ppc64" \
> CXX="g++ -arch i386 -arch x86_64 -arch ppc -arch ppc64" \
> CPP="gcc -E" CXXCPP="g++ -E"
>
> This is not guaranteed to produce working output in all cases, you
> may have to build one architecture at a time and combine the results
> using the `lipo' tool if you have problems.
>
103c144
< By default, `make install' installs the package's commands under
---
> By default, `make install' installs the package's commands under
106c147,148
< `configure' the option `--prefix=PREFIX'.
---
> `configure' the option `--prefix=PREFIX', where PREFIX must be an
> absolute file name.
117c159,162
< you can set and what kinds of files go in them.
---
> 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.
119,121c164,168
< 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
< option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
---
> The most portable way to affect installation locations is to pass the
> correct locations to `configure'; however, many packages provide one or
> both of the following shortcuts of passing variable assignments to the
> `make install' command line to change installation locations without
> having to reconfigure or recompile.
122a170,191
> The first method involves providing an override variable for each
> affected directory. For example, `make install
> 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.
>
> The second method involves providing the `DESTDIR' variable. For
> example, `make install DESTDIR=/alternate/directory' will prepend
> `/alternate/directory' before all installation names. The approach of
> `DESTDIR' overrides is not required by the GNU Coding Standards, and
> does not work on platforms that have drive letters. On the other hand,
> it does better at avoiding recompilation issues, and works well even
> when some directory options were not specified in terms of `${prefix}'
> at `configure' time.
>
126c195,199
< Some packages pay attention to `--enable-FEATURE' options to
---
> 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
> option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
>
> Some packages pay attention to `--enable-FEATURE' options to
137a211,249
> Some packages offer the ability to configure how verbose the
> execution of `make' will be. For these packages, running `./configure
> --enable-silent-rules' sets the default to minimal output, which can be
> overridden with `make V=1'; while running `./configure
> --disable-silent-rules' sets the default to verbose, which can be
> overridden with `make V=0'.
>
> 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
> 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
>
> ./configure CC="cc"
>
> and if that doesn't work, try
>
> ./configure CC="cc -nodtk"
>
> On Solaris, don't put `/usr/ucb' early in your `PATH'. This
> directory contains several dysfunctional programs; working variants of
> these programs are available in `/usr/bin'. So, if you need `/usr/ucb'
> in your `PATH', put it _after_ `/usr/bin'.
>
> On Haiku, software installed for all users goes in `/boot/common',
> not `/usr/local'. It is recommended to use the following options:
>
> ./configure --prefix=/boot/common
>
141,145c253,257
< There may be some features `configure' cannot figure out automatically,
< but needs to determine by the type of machine the package will run on.
< Usually, assuming the package is built to be run on the _same_
< architectures, `configure' can figure that out, but if it prints a
< message saying it cannot guess the machine type, give it the
---
> There may be some features `configure' cannot figure out
> automatically, but needs to determine by the type of machine the package
> will run on. Usually, assuming the package is built to be run on the
> _same_ architectures, `configure' can figure that out, but if it prints
> a message saying it cannot guess the machine type, give it the
153c265,266
< OS KERNEL-OS
---
> OS
> KERNEL-OS
171,173c284,286
< If you want to set default values for `configure' scripts to share, you
< can create a site shell script called `config.site' that gives default
< values for variables like `CC', `cache_file', and `prefix'.
---
> If you want to set default values for `configure' scripts to share,
> you can create a site shell script called `config.site' that gives
> default values for variables like `CC', `cache_file', and `prefix'.
182c295
< Variables not defined in a site shell script can be set in the
---
> Variables not defined in a site shell script can be set in the
201c314,315
< `configure' recognizes the following options to control how it operates.
---
> `configure' recognizes the following options to control how it
> operates.
205c319
< Print a summary of the options to `configure', and exit.
---
> Print a summary of all of the options to `configure', and exit.
206a321,327
> `--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.
>
231a353,362
> `--prefix=DIR'
> 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'
> Run the configure checks, but stop before creating any output
> files.
>