1. Note: logwtmp plugin source file patchlevel.h must match pppd version
  2. on system if it is used. Edit the file plugins/patchlevel.h
  3. accordingly.
  4. --
  5. Basic Installation
  6. ==================
  7. These are generic installation instructions.
  8. The `configure' shell script attempts to guess correct values for
  9. various system-dependent variables used during compilation. It uses
  10. those values to create a `Makefile' in each directory of the package.
  11. It may also create one or more `.h' files containing system-dependent
  12. definitions. Finally, it creates a shell script `config.status' that
  13. you can run in the future to recreate the current configuration, a file
  14. `config.cache' that saves the results of its tests to speed up
  15. reconfiguring, and a file `config.log' containing compiler output
  16. (useful mainly for debugging `configure').
  17. If you need to do unusual things to compile the package, please try
  18. to figure out how `configure' could check whether to do them, and mail
  19. diffs or instructions to the address given in the `README' so they can
  20. be considered for the next release. If at some point `config.cache'
  21. contains results you don't want to keep, you may remove or edit it.
  22. The file `' is used to create `configure' by a program
  23. called `autoconf'. You only need `' if you want to change
  24. it or regenerate `configure' using a newer version of `autoconf'.
  25. The simplest way to compile this package is:
  26. 1. `cd' to the directory containing the package's source code and type
  27. `./configure' to configure the package for your system. If you're
  28. using `csh' on an old version of System V, you might need to type
  29. `sh ./configure' instead to prevent `csh' from trying to execute
  30. `configure' itself.
  31. Running `configure' takes awhile. While running, it prints some
  32. messages telling which features it is checking for.
  33. 2. Type `make' to compile the package.
  34. 3. Optionally, type `make check' to run any self-tests that come with
  35. the package.
  36. 4. Type `make install' to install the programs and any data files and
  37. documentation.
  38. 5. You can remove the program binaries and object files from the
  39. source code directory by typing `make clean'. To also remove the
  40. files that `configure' created (so you can compile the package for
  41. a different kind of computer), type `make distclean'. There is
  42. also a `make maintainer-clean' target, but that is intended mainly
  43. for the package's developers. If you use it, you may have to get
  44. all sorts of other programs in order to regenerate files that came
  45. with the distribution.
  46. Compilers and Options
  47. =====================
  48. Some systems require unusual options for compilation or linking that
  49. the `configure' script does not know about. You can give `configure'
  50. initial values for variables by setting them in the environment. Using
  51. a Bourne-compatible shell, you can do that on the command line like
  52. this:
  53. CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure
  54. Or on systems that have the `env' program, you can do it like this:
  55. env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure
  56. Compiling For Multiple Architectures
  57. ====================================
  58. You can compile the package for more than one kind of computer at the
  59. same time, by placing the object files for each architecture in their
  60. own directory. To do this, you must use a version of `make' that
  61. supports the `VPATH' variable, such as GNU `make'. `cd' to the
  62. directory where you want the object files and executables to go and run
  63. the `configure' script. `configure' automatically checks for the
  64. source code in the directory that `configure' is in and in `..'.
  65. If you have to use a `make' that does not supports the `VPATH'
  66. variable, you have to compile the package for one architecture at a time
  67. in the source code directory. After you have installed the package for
  68. one architecture, use `make distclean' before reconfiguring for another
  69. architecture.
  70. Installation Names
  71. ==================
  72. By default, `make install' will install the package's files in
  73. `/usr/local/bin', `/usr/local/man', etc. You can specify an
  74. installation prefix other than `/usr/local' by giving `configure' the
  75. option `--prefix=PATH'.
  76. You can specify separate installation prefixes for
  77. architecture-specific files and architecture-independent files. If you
  78. give `configure' the option `--exec-prefix=PATH', the package will use
  79. PATH as the prefix for installing programs and libraries.
  80. Documentation and other data files will still use the regular prefix.
  81. In addition, if you use an unusual directory layout you can give
  82. options like `--bindir=PATH' to specify different values for particular
  83. kinds of files. Run `configure --help' for a list of the directories
  84. you can set and what kinds of files go in them.
  85. If the package supports it, you can cause programs to be installed
  86. with an extra prefix or suffix on their names by giving `configure' the
  87. option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
  88. Optional Features
  89. =================
  90. Some packages pay attention to `--enable-FEATURE' options to
  91. `configure', where FEATURE indicates an optional part of the package.
  92. They may also pay attention to `--with-PACKAGE' options, where PACKAGE
  93. is something like `gnu-as' or `x' (for the X Window System). The
  94. `README' should mention any `--enable-' and `--with-' options that the
  95. package recognizes.
  96. For packages that use the X Window System, `configure' can usually
  97. find the X include and library files automatically, but if it doesn't,
  98. you can use the `configure' options `--x-includes=DIR' and
  99. `--x-libraries=DIR' to specify their locations.
  100. Specifying the System Type
  101. ==========================
  102. There may be some features `configure' can not figure out
  103. automatically, but needs to determine by the type of host the package
  104. will run on. Usually `configure' can figure that out, but if it prints
  105. a message saying it can not guess the host type, give it the
  106. `--host=TYPE' option. TYPE can either be a short name for the system
  107. type, such as `sun4', or a canonical name with three fields:
  109. See the file `config.sub' for the possible values of each field. If
  110. `config.sub' isn't included in this package, then this package doesn't
  111. need to know the host type.
  112. If you are building compiler tools for cross-compiling, you can also
  113. use the `--target=TYPE' option to select the type of system they will
  114. produce code for and the `--build=TYPE' option to select the type of
  115. system on which you are compiling the package.
  116. Sharing Defaults
  117. ================
  118. If you want to set default values for `configure' scripts to share,
  119. you can create a site shell script called `' that gives
  120. default values for variables like `CC', `cache_file', and `prefix'.
  121. `configure' looks for `PREFIX/share/' if it exists, then
  122. `PREFIX/etc/' if it exists. Or, you can set the
  123. `CONFIG_SITE' environment variable to the location of the site script.
  124. A warning: not all `configure' scripts look for a site script.
  125. Operation Controls
  126. ==================
  127. `configure' recognizes the following options to control how it
  128. operates.
  129. `--cache-file=FILE'
  130. Use and save the results of the tests in FILE instead of
  131. `./config.cache'. Set FILE to `/dev/null' to disable caching, for
  132. debugging `configure'.
  133. `--help'
  134. Print a summary of the options to `configure', and exit.
  135. `--quiet'
  136. `--silent'
  137. `-q'
  138. Do not print messages saying which checks are being made. To
  139. suppress all normal output, redirect it to `/dev/null' (any error
  140. messages will still be shown).
  141. `--srcdir=DIR'
  142. Look for the package's source code in directory DIR. Usually
  143. `configure' can determine that directory automatically.
  144. `--version'
  145. Print the version of Autoconf used to generate the `configure'
  146. script, and exit.
  147. `configure' also accepts some other, not widely useful, options.