You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

INSTALL 7.6KB

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