-Installation Instructions\r
-*************************\r
-\r
-Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005 Free\r
-Software Foundation, Inc.\r
-\r
-This file is free documentation; the Free Software Foundation gives\r
-unlimited permission to copy, distribute and modify it.\r
-\r
-Basic Installation\r
-==================\r
-\r
-These are generic installation instructions.\r
-\r
- The `configure' shell script attempts to guess correct values for\r
-various system-dependent variables used during compilation. It uses\r
-those values to create a `Makefile' in each directory of the package.\r
-It may also create one or more `.h' files containing system-dependent\r
-definitions. Finally, it creates a shell script `config.status' that\r
-you can run in the future to recreate the current configuration, and a\r
-file `config.log' containing compiler output (useful mainly for\r
-debugging `configure').\r
-\r
- It can also use an optional file (typically called `config.cache'\r
-and enabled with `--cache-file=config.cache' or simply `-C') that saves\r
-the results of its tests to speed up reconfiguring. (Caching is\r
-disabled by default to prevent problems with accidental use of stale\r
-cache files.)\r
-\r
- If you need to do unusual things to compile the package, please try\r
-to figure out how `configure' could check whether to do them, and mail\r
-diffs or instructions to the address given in the `README' so they can\r
-be considered for the next release. If you are using the cache, and at\r
-some point `config.cache' contains results you don't want to keep, you\r
-may remove or edit it.\r
-\r
- The file `configure.ac' (or `configure.in') is used to create\r
-`configure' by a program called `autoconf'. You only need\r
-`configure.ac' if you want to change it or regenerate `configure' using\r
-a newer version of `autoconf'.\r
-\r
-The simplest way to compile this package is:\r
-\r
- 1. `cd' to the directory containing the package's source code and type\r
- `./configure' to configure the package for your system. If you're\r
- using `csh' on an old version of System V, you might need to type\r
- `sh ./configure' instead to prevent `csh' from trying to execute\r
- `configure' itself.\r
-\r
- Running `configure' takes awhile. While running, it prints some\r
- messages telling which features it is checking for.\r
-\r
- 2. Type `make' to compile the package.\r
-\r
- 3. Optionally, type `make check' to run any self-tests that come with\r
- the package.\r
-\r
- 4. Type `make install' to install the programs and any data files and\r
- documentation.\r
-\r
- 5. You can remove the program binaries and object files from the\r
- source code directory by typing `make clean'. To also remove the\r
- files that `configure' created (so you can compile the package for\r
- a different kind of computer), type `make distclean'. There is\r
- also a `make maintainer-clean' target, but that is intended mainly\r
- for the package's developers. If you use it, you may have to get\r
- all sorts of other programs in order to regenerate files that came\r
- with the distribution.\r
-\r
-Compilers and Options\r
-=====================\r
-\r
-Some systems require unusual options for compilation or linking that the\r
-`configure' script does not know about. Run `./configure --help' for\r
-details on some of the pertinent environment variables.\r
-\r
- You can give `configure' initial values for configuration parameters\r
-by setting variables in the command line or in the environment. Here\r
-is an example:\r
-\r
- ./configure CC=c89 CFLAGS=-O2 LIBS=-lposix\r
-\r
- *Note Defining Variables::, for more details.\r
-\r
-Compiling For Multiple Architectures\r
-====================================\r
-\r
-You can compile the package for more than one kind of computer at the\r
-same time, by placing the object files for each architecture in their\r
-own directory. To do this, you must use a version of `make' that\r
-supports the `VPATH' variable, such as GNU `make'. `cd' to the\r
-directory where you want the object files and executables to go and run\r
-the `configure' script. `configure' automatically checks for the\r
-source code in the directory that `configure' is in and in `..'.\r
-\r
- If you have to use a `make' that does not support the `VPATH'\r
-variable, you have to compile the package for one architecture at a\r
-time in the source code directory. After you have installed the\r
-package for one architecture, use `make distclean' before reconfiguring\r
-for another architecture.\r
-\r
-Installation Names\r
-==================\r
-\r
-By default, `make install' installs the package's commands under\r
-`/usr/local/bin', include files under `/usr/local/include', etc. You\r
-can specify an installation prefix other than `/usr/local' by giving\r
-`configure' the option `--prefix=PREFIX'.\r
-\r
- You can specify separate installation prefixes for\r
-architecture-specific files and architecture-independent files. If you\r
-pass the option `--exec-prefix=PREFIX' to `configure', the package uses\r
-PREFIX as the prefix for installing programs and libraries.\r
-Documentation and other data files still use the regular prefix.\r
-\r
- In addition, if you use an unusual directory layout you can give\r
-options like `--bindir=DIR' to specify different values for particular\r
-kinds of files. Run `configure --help' for a list of the directories\r
-you can set and what kinds of files go in them.\r
-\r
- If the package supports it, you can cause programs to be installed\r
-with an extra prefix or suffix on their names by giving `configure' the\r
-option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.\r
-\r
-Optional Features\r
-=================\r
-\r
-Some packages pay attention to `--enable-FEATURE' options to\r
-`configure', where FEATURE indicates an optional part of the package.\r
-They may also pay attention to `--with-PACKAGE' options, where PACKAGE\r
-is something like `gnu-as' or `x' (for the X Window System). The\r
-`README' should mention any `--enable-' and `--with-' options that the\r
-package recognizes.\r
-\r
- For packages that use the X Window System, `configure' can usually\r
-find the X include and library files automatically, but if it doesn't,\r
-you can use the `configure' options `--x-includes=DIR' and\r
-`--x-libraries=DIR' to specify their locations.\r
-\r
-Specifying the System Type\r
-==========================\r
-\r
-There may be some features `configure' cannot figure out automatically,\r
-but needs to determine by the type of machine the package will run on.\r
-Usually, assuming the package is built to be run on the _same_\r
-architectures, `configure' can figure that out, but if it prints a\r
-message saying it cannot guess the machine type, give it the\r
-`--build=TYPE' option. TYPE can either be a short name for the system\r
-type, such as `sun4', or a canonical name which has the form:\r
-\r
- CPU-COMPANY-SYSTEM\r
-\r
-where SYSTEM can have one of these forms:\r
-\r
- OS KERNEL-OS\r
-\r
- See the file `config.sub' for the possible values of each field. If\r
-`config.sub' isn't included in this package, then this package doesn't\r
-need to know the machine type.\r
-\r
- If you are _building_ compiler tools for cross-compiling, you should\r
-use the option `--target=TYPE' to select the type of system they will\r
-produce code for.\r
-\r
- If you want to _use_ a cross compiler, that generates code for a\r
-platform different from the build platform, you should specify the\r
-"host" platform (i.e., that on which the generated programs will\r
-eventually be run) with `--host=TYPE'.\r
-\r
-Sharing Defaults\r
-================\r
-\r
-If you want to set default values for `configure' scripts to share, you\r
-can create a site shell script called `config.site' that gives default\r
-values for variables like `CC', `cache_file', and `prefix'.\r
-`configure' looks for `PREFIX/share/config.site' if it exists, then\r
-`PREFIX/etc/config.site' if it exists. Or, you can set the\r
-`CONFIG_SITE' environment variable to the location of the site script.\r
-A warning: not all `configure' scripts look for a site script.\r
-\r
-Defining Variables\r
-==================\r
-\r
-Variables not defined in a site shell script can be set in the\r
-environment passed to `configure'. However, some packages may run\r
-configure again during the build, and the customized values of these\r
-variables may be lost. In order to avoid this problem, you should set\r
-them in the `configure' command line, using `VAR=value'. For example:\r
-\r
- ./configure CC=/usr/local2/bin/gcc\r
-\r
-causes the specified `gcc' to be used as the C compiler (unless it is\r
-overridden in the site shell script). Here is a another example:\r
-\r
- /bin/bash ./configure CONFIG_SHELL=/bin/bash\r
-\r
-Here the `CONFIG_SHELL=/bin/bash' operand causes subsequent\r
-configuration-related scripts to be executed by `/bin/bash'.\r
-\r
-`configure' Invocation\r
-======================\r
-\r
-`configure' recognizes the following options to control how it operates.\r
-\r
-`--help'\r
-`-h'\r
- Print a summary of the options to `configure', and exit.\r
-\r
-`--version'\r
-`-V'\r
- Print the version of Autoconf used to generate the `configure'\r
- script, and exit.\r
-\r
-`--cache-file=FILE'\r
- Enable the cache: use and save the results of the tests in FILE,\r
- traditionally `config.cache'. FILE defaults to `/dev/null' to\r
- disable caching.\r
-\r
-`--config-cache'\r
-`-C'\r
- Alias for `--cache-file=config.cache'.\r
-\r
-`--quiet'\r
-`--silent'\r
-`-q'\r
- Do not print messages saying which checks are being made. To\r
- suppress all normal output, redirect it to `/dev/null' (any error\r
- messages will still be shown).\r
-\r
-`--srcdir=DIR'\r
- Look for the package's source code in directory DIR. Usually\r
- `configure' can determine that directory automatically.\r
-\r
-`configure' also accepts some other, not widely useful, options. Run\r
-`configure --help' for more details.\r
-\r
+Installation Instructions
+*************************
+
+Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005 Free
+Software Foundation, Inc.
+
+This file is free documentation; the Free Software Foundation gives
+unlimited permission to copy, distribute and modify it.
+
+Basic Installation
+==================
+
+These are generic installation instructions.
+
+ The `configure' shell script attempts to guess correct values for
+various system-dependent variables used during compilation. It uses
+those values to create a `Makefile' in each directory of the package.
+It may also create one or more `.h' files containing system-dependent
+definitions. Finally, it creates a shell script `config.status' that
+you can run in the future to recreate the current configuration, and a
+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.)
+
+ 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
+diffs or instructions to the address given in the `README' so they can
+be considered for the next release. If you are using the cache, and at
+some point `config.cache' contains results you don't want to keep, you
+may remove or edit it.
+
+ The file `configure.ac' (or `configure.in') is used to create
+`configure' by a program called `autoconf'. You only need
+`configure.ac' if you want to change it or regenerate `configure' using
+a newer version of `autoconf'.
+
+The simplest way to compile this package is:
+
+ 1. `cd' to the directory containing the package's source code and type
+ `./configure' to configure the package for your system. If you're
+ using `csh' on an old version of System V, you might need to type
+ `sh ./configure' instead to prevent `csh' from trying to execute
+ `configure' itself.
+
+ Running `configure' takes awhile. While running, it prints some
+ messages telling which features it is checking for.
+
+ 2. Type `make' to compile the package.
+
+ 3. Optionally, type `make check' to run any self-tests that come with
+ the package.
+
+ 4. Type `make install' to install the programs and any data files and
+ documentation.
+
+ 5. You can remove the program binaries and object files from the
+ source code directory by typing `make clean'. To also remove the
+ files that `configure' created (so you can compile the package for
+ a different kind of computer), type `make distclean'. There is
+ also a `make maintainer-clean' target, but that is intended mainly
+ for the package's developers. If you use it, you may have to get
+ all sorts of other programs in order to regenerate files that came
+ with the distribution.
+
+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:
+
+ ./configure CC=c89 CFLAGS=-O2 LIBS=-lposix
+
+ *Note Defining Variables::, for more details.
+
+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 must use a version of `make' that
+supports the `VPATH' variable, such as 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 `..'.
+
+ If you have to use a `make' that does not support the `VPATH'
+variable, you have to compile the package for one architecture at a
+time in the source code directory. After you have installed the
+package for one architecture, use `make distclean' before reconfiguring
+for another architecture.
+
+Installation Names
+==================
+
+By default, `make install' installs the package's commands under
+`/usr/local/bin', include files under `/usr/local/include', etc. You
+can specify an installation prefix other than `/usr/local' by giving
+`configure' the option `--prefix=PREFIX'.
+
+ You can specify separate installation prefixes for
+architecture-specific files and architecture-independent files. If you
+pass the option `--exec-prefix=PREFIX' to `configure', the package uses
+PREFIX as the prefix for installing programs and libraries.
+Documentation and other data files still use the regular prefix.
+
+ 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.
+
+ 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'.
+
+Optional Features
+=================
+
+Some packages pay attention to `--enable-FEATURE' options to
+`configure', where FEATURE indicates an optional part of the package.
+They may also pay attention to `--with-PACKAGE' options, where PACKAGE
+is something like `gnu-as' or `x' (for the X Window System). The
+`README' should mention any `--enable-' and `--with-' options that the
+package recognizes.
+
+ For packages that use the X Window System, `configure' can usually
+find the X include and library files automatically, but if it doesn't,
+you can use the `configure' options `--x-includes=DIR' and
+`--x-libraries=DIR' to specify their locations.
+
+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 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
+`--build=TYPE' option. TYPE can either be a short name for the system
+type, such as `sun4', or a canonical name which has the form:
+
+ CPU-COMPANY-SYSTEM
+
+where SYSTEM can have one of these forms:
+
+ OS KERNEL-OS
+
+ See the file `config.sub' for the possible values of each field. If
+`config.sub' isn't included in this package, then this package doesn't
+need to know the machine type.
+
+ If you are _building_ compiler tools for cross-compiling, you should
+use the option `--target=TYPE' to select the type of system they will
+produce code for.
+
+ If you want to _use_ a cross compiler, that generates code for a
+platform different from the build platform, you should specify the
+"host" platform (i.e., that on which the generated programs will
+eventually be run) with `--host=TYPE'.
+
+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 default
+values for variables like `CC', `cache_file', and `prefix'.
+`configure' looks for `PREFIX/share/config.site' if it exists, then
+`PREFIX/etc/config.site' if it exists. Or, you can set the
+`CONFIG_SITE' environment variable to the location of the site script.
+A warning: not all `configure' scripts look for a site script.
+
+Defining Variables
+==================
+
+Variables not defined in a site shell script can be set in the
+environment passed to `configure'. However, some packages may run
+configure again during the build, and the customized values of these
+variables may be lost. In order to avoid this problem, you should set
+them in the `configure' command line, using `VAR=value'. For example:
+
+ ./configure CC=/usr/local2/bin/gcc
+
+causes the specified `gcc' to be used as the C compiler (unless it is
+overridden in the site shell script). Here is a another example:
+
+ /bin/bash ./configure CONFIG_SHELL=/bin/bash
+
+Here the `CONFIG_SHELL=/bin/bash' operand causes subsequent
+configuration-related scripts to be executed by `/bin/bash'.
+
+`configure' Invocation
+======================
+
+`configure' recognizes the following options to control how it operates.
+
+`--help'
+`-h'
+ Print a summary of the options to `configure', and exit.
+
+`--version'
+`-V'
+ Print the version of Autoconf used to generate the `configure'
+ script, and exit.
+
+`--cache-file=FILE'
+ Enable the cache: use and save the results of the tests in FILE,
+ traditionally `config.cache'. FILE defaults to `/dev/null' to
+ disable caching.
+
+`--config-cache'
+`-C'
+ Alias for `--cache-file=config.cache'.
+
+`--quiet'
+`--silent'
+`-q'
+ Do not print messages saying which checks are being made. To
+ suppress all normal output, redirect it to `/dev/null' (any error
+ messages will still be shown).
+
+`--srcdir=DIR'
+ Look for the package's source code in directory DIR. Usually
+ `configure' can determine that directory automatically.
+
+`configure' also accepts some other, not widely useful, options. Run
+`configure --help' for more details.
+
Code Review / simantics / platform.git / blobdiff