Permalink
Browse files

Initial commit

  • Loading branch information...
0 parents commit e39021ff8ae5651b96790b83e85dd593d223044a Nick Foster committed Sep 15, 2010
Showing with 21,343 additions and 0 deletions.
  1. +1 −0 AUTHORS
  2. +674 −0 COPYING
  3. +25 −0 ChangeLog
  4. +365 −0 INSTALL
  5. +33 −0 Makefile.am
  6. +67 −0 Makefile.common
  7. 0 NEWS
  8. +50 −0 README
  9. +29 −0 bootstrap
  10. +293 −0 config/.svn/all-wcprops
  11. +20 −0 config/.svn/dir-prop-base
  12. +651 −0 config/.svn/entries
  13. +1 −0 config/.svn/format
  14. +9 −0 config/.svn/prop-base/Makefile.am.svn-base
  15. +9 −0 config/.svn/prop-base/acx_pthread.m4.svn-base
  16. +5 −0 config/.svn/prop-base/ax_boost_base.m4.svn-base
  17. +5 −0 config/.svn/prop-base/ax_boost_date_time.m4.svn-base
  18. +5 −0 config/.svn/prop-base/ax_boost_filesystem.m4.svn-base
  19. +5 −0 config/.svn/prop-base/ax_boost_iostreams.m4.svn-base
  20. +5 −0 config/.svn/prop-base/ax_boost_program_options.m4.svn-base
  21. +5 −0 config/.svn/prop-base/ax_boost_python.m4.svn-base
  22. +5 −0 config/.svn/prop-base/ax_boost_regex.m4.svn-base
  23. +5 −0 config/.svn/prop-base/ax_boost_serialization.m4.svn-base
  24. +5 −0 config/.svn/prop-base/ax_boost_signals.m4.svn-base
  25. +5 −0 config/.svn/prop-base/ax_boost_system.m4.svn-base
  26. +5 −0 config/.svn/prop-base/ax_boost_test_exec_monitor.m4.svn-base
  27. +5 −0 config/.svn/prop-base/ax_boost_thread.m4.svn-base
  28. +5 −0 config/.svn/prop-base/ax_boost_unit_test_framework.m4.svn-base
  29. +5 −0 config/.svn/prop-base/ax_boost_wserialization.m4.svn-base
  30. +9 −0 config/.svn/prop-base/bnv_have_qt.m4.svn-base
  31. +9 −0 config/.svn/prop-base/cppunit.m4.svn-base
  32. +9 −0 config/.svn/prop-base/gr_check_createfilemapping.m4.svn-base
  33. +9 −0 config/.svn/prop-base/gr_check_mc4020.m4.svn-base
  34. +9 −0 config/.svn/prop-base/gr_check_shm_open.m4.svn-base
  35. +9 −0 config/.svn/prop-base/gr_check_usrp.m4.svn-base
  36. +9 −0 config/.svn/prop-base/gr_doxygen.m4.svn-base
  37. +5 −0 config/.svn/prop-base/gr_fortran.m4.svn-base
  38. +9 −0 config/.svn/prop-base/gr_gprof.m4.svn-base
  39. +9 −0 config/.svn/prop-base/gr_lib64.m4.svn-base
  40. +9 −0 config/.svn/prop-base/gr_libgnuradio_core_extra_ldflags.m4.svn-base
  41. +9 −0 config/.svn/prop-base/gr_no_undefined.m4.svn-base
  42. +9 −0 config/.svn/prop-base/gr_omnithread.m4.svn-base
  43. +9 −0 config/.svn/prop-base/gr_pwin32.m4.svn-base
  44. +9 −0 config/.svn/prop-base/gr_python.m4.svn-base
  45. +9 −0 config/.svn/prop-base/gr_require_mc4020.m4.svn-base
  46. +9 −0 config/.svn/prop-base/gr_scripting.m4.svn-base
  47. +9 −0 config/.svn/prop-base/gr_set_md_cpu.m4.svn-base
  48. +5 −0 config/.svn/prop-base/gr_standalone.m4.svn-base
  49. +9 −0 config/.svn/prop-base/gr_swig.m4.svn-base
  50. +9 −0 config/.svn/prop-base/gr_sysv_shm.m4.svn-base
  51. +9 −0 config/.svn/prop-base/lf_cc.m4.svn-base
  52. +9 −0 config/.svn/prop-base/lf_cxx.m4.svn-base
  53. +9 −0 config/.svn/prop-base/lf_warnings.m4.svn-base
  54. +9 −0 config/.svn/prop-base/lf_x11.m4.svn-base
  55. +9 −0 config/.svn/prop-base/mkstemp.m4.svn-base
  56. +9 −0 config/.svn/prop-base/onceonly.m4.svn-base
  57. +9 −0 config/.svn/prop-base/pkg.m4.svn-base
  58. +9 −0 config/.svn/prop-base/usrp_fusb_tech.m4.svn-base
  59. +9 −0 config/.svn/prop-base/usrp_libusb.m4.svn-base
  60. +9 −0 config/.svn/prop-base/usrp_sdcc.m4.svn-base
  61. +81 −0 config/.svn/text-base/Makefile.am.svn-base
  62. +275 −0 config/.svn/text-base/acx_pthread.m4.svn-base
  63. +334 −0 config/.svn/text-base/ax_boost_base.m4.svn-base
  64. +34 −0 config/.svn/text-base/ax_boost_date_time.m4.svn-base
  65. +45 −0 config/.svn/text-base/ax_boost_filesystem.m4.svn-base
  66. +39 −0 config/.svn/text-base/ax_boost_iostreams.m4.svn-base
  67. +35 −0 config/.svn/text-base/ax_boost_program_options.m4.svn-base
  68. +92 −0 config/.svn/text-base/ax_boost_python.m4.svn-base
  69. +35 −0 config/.svn/text-base/ax_boost_regex.m4.svn-base
  70. +38 −0 config/.svn/text-base/ax_boost_serialization.m4.svn-base
  71. +35 −0 config/.svn/text-base/ax_boost_signals.m4.svn-base
  72. +40 −0 config/.svn/text-base/ax_boost_system.m4.svn-base
  73. +35 −0 config/.svn/text-base/ax_boost_test_exec_monitor.m4.svn-base
  74. +72 −0 config/.svn/text-base/ax_boost_thread.m4.svn-base
  75. +36 −0 config/.svn/text-base/ax_boost_unit_test_framework.m4.svn-base
  76. +46 −0 config/.svn/text-base/ax_boost_wserialization.m4.svn-base
  77. +404 −0 config/.svn/text-base/bnv_have_qt.m4.svn-base
  78. +80 −0 config/.svn/text-base/cppunit.m4.svn-base
  79. +52 −0 config/.svn/text-base/gr_check_createfilemapping.m4.svn-base
  80. +37 −0 config/.svn/text-base/gr_check_mc4020.m4.svn-base
  81. +29 −0 config/.svn/text-base/gr_check_shm_open.m4.svn-base
  82. +32 −0 config/.svn/text-base/gr_check_usrp.m4.svn-base
  83. +60 −0 config/.svn/text-base/gr_doxygen.m4.svn-base
  84. +32 −0 config/.svn/text-base/gr_fortran.m4.svn-base
  85. +72 −0 config/.svn/text-base/gr_gprof.m4.svn-base
  86. +85 −0 config/.svn/text-base/gr_lib64.m4.svn-base
  87. +40 −0 config/.svn/text-base/gr_libgnuradio_core_extra_ldflags.m4.svn-base
  88. +44 −0 config/.svn/text-base/gr_no_undefined.m4.svn-base
  89. +52 −0 config/.svn/text-base/gr_omnithread.m4.svn-base
  90. +146 −0 config/.svn/text-base/gr_pwin32.m4.svn-base
  91. +128 −0 config/.svn/text-base/gr_python.m4.svn-base
  92. +33 −0 config/.svn/text-base/gr_require_mc4020.m4.svn-base
  93. +30 −0 config/.svn/text-base/gr_scripting.m4.svn-base
  94. +44 −0 config/.svn/text-base/gr_set_md_cpu.m4.svn-base
  95. +119 −0 config/.svn/text-base/gr_standalone.m4.svn-base
  96. +36 −0 config/.svn/text-base/gr_subversion.m4.svn-base
  97. +85 −0 config/.svn/text-base/gr_swig.m4.svn-base
  98. +36 −0 config/.svn/text-base/gr_sysv_shm.m4.svn-base
  99. +41 −0 config/.svn/text-base/lf_cc.m4.svn-base
  100. +67 −0 config/.svn/text-base/lf_cxx.m4.svn-base
  101. +128 −0 config/.svn/text-base/lf_warnings.m4.svn-base
  102. +39 −0 config/.svn/text-base/lf_x11.m4.svn-base
  103. +89 −0 config/.svn/text-base/mkstemp.m4.svn-base
  104. +63 −0 config/.svn/text-base/onceonly.m4.svn-base
  105. +188 −0 config/.svn/text-base/pkg.m4.svn-base
  106. +74 −0 config/.svn/text-base/usrp_fusb_tech.m4.svn-base
  107. +48 −0 config/.svn/text-base/usrp_libusb.m4.svn-base
  108. +75 −0 config/.svn/text-base/usrp_sdcc.m4.svn-base
  109. +558 −0 config/Makefile
  110. +81 −0 config/Makefile.am
  111. +558 −0 config/Makefile.in
  112. +275 −0 config/acx_pthread.m4
  113. +334 −0 config/ax_boost_base.m4
  114. +34 −0 config/ax_boost_date_time.m4
  115. +45 −0 config/ax_boost_filesystem.m4
  116. +39 −0 config/ax_boost_iostreams.m4
  117. +35 −0 config/ax_boost_program_options.m4
  118. +92 −0 config/ax_boost_python.m4
  119. +35 −0 config/ax_boost_regex.m4
  120. +38 −0 config/ax_boost_serialization.m4
  121. +35 −0 config/ax_boost_signals.m4
  122. +40 −0 config/ax_boost_system.m4
  123. +35 −0 config/ax_boost_test_exec_monitor.m4
  124. +72 −0 config/ax_boost_thread.m4
  125. +36 −0 config/ax_boost_unit_test_framework.m4
  126. +46 −0 config/ax_boost_wserialization.m4
  127. +404 −0 config/bnv_have_qt.m4
  128. +80 −0 config/cppunit.m4
  129. +52 −0 config/gr_check_createfilemapping.m4
  130. +37 −0 config/gr_check_mc4020.m4
  131. +29 −0 config/gr_check_shm_open.m4
  132. +32 −0 config/gr_check_usrp.m4
  133. +60 −0 config/gr_doxygen.m4
  134. +32 −0 config/gr_fortran.m4
  135. +72 −0 config/gr_gprof.m4
  136. +85 −0 config/gr_lib64.m4
  137. +40 −0 config/gr_libgnuradio_core_extra_ldflags.m4
  138. +44 −0 config/gr_no_undefined.m4
  139. +52 −0 config/gr_omnithread.m4
  140. +146 −0 config/gr_pwin32.m4
  141. +128 −0 config/gr_python.m4
  142. +33 −0 config/gr_require_mc4020.m4
  143. +30 −0 config/gr_scripting.m4
  144. +44 −0 config/gr_set_md_cpu.m4
  145. +119 −0 config/gr_standalone.m4
  146. +36 −0 config/gr_subversion.m4
  147. +85 −0 config/gr_swig.m4
  148. +36 −0 config/gr_sysv_shm.m4
  149. +41 −0 config/lf_cc.m4
  150. +67 −0 config/lf_cxx.m4
  151. +128 −0 config/lf_warnings.m4
  152. +39 −0 config/lf_x11.m4
  153. +7,377 −0 config/libtool.m4
  154. +368 −0 config/ltoptions.m4
  155. +123 −0 config/ltsugar.m4
  156. +23 −0 config/ltversion.m4
  157. +92 −0 config/lt~obsolete.m4
  158. +89 −0 config/mkstemp.m4
  159. +63 −0 config/onceonly.m4
  160. +188 −0 config/pkg.m4
  161. +74 −0 config/usrp_fusb_tech.m4
  162. +48 −0 config/usrp_libusb.m4
  163. +75 −0 config/usrp_sdcc.m4
  164. +75 −0 configure.ac
  165. +22 −0 src/Makefile.am
  166. +84 −0 src/lib/Makefile.am
  167. +52 −0 src/lib/air.i
  168. +92 −0 src/lib/air_modes_framer.cc
  169. +33 −0 src/lib/air_modes_framer.h
  170. +147 −0 src/lib/air_modes_preamble.cc
  171. +35 −0 src/lib/air_modes_preamble.h
  172. +220 −0 src/lib/air_modes_slicer.cc
  173. +35 −0 src/lib/air_modes_slicer.h
  174. +19 −0 src/lib/air_modes_types.h
  175. +30 −0 src/lib/modes_energy.cc
  176. +4 −0 src/lib/modes_energy.h
  177. +256 −0 src/lib/modes_parity.cc
  178. +8 −0 src/lib/modes_parity.h
  179. +32 −0 src/python/Makefile.am
  180. +71 −0 src/python/altitude.py
  181. BIN src/python/altitude.pyc
  182. +38 −0 src/python/cpr-test.py
  183. +246 −0 src/python/cpr.py
  184. BIN src/python/cpr.pyc
  185. +247 −0 src/python/modes_parse.py
  186. BIN src/python/modes_parse.pyc
  187. +142 −0 src/python/modes_print.py
  188. +85 −0 src/python/modes_sql.py
  189. +183 −0 src/python/usrp_modes.py
@@ -0,0 +1 @@
+Eric Blossom <eb@comsec.com>
674 COPYING

Large diffs are not rendered by default.

Oops, something went wrong.
@@ -0,0 +1,25 @@
+#
+# Copyright 2001,2002,2003,2004,2005,2006,2007 Free Software Foundation, Inc.
+#
+# This file is part of GNU Radio
+#
+# GNU Radio is free software; you can redistribute it and/or modify
+# it under the terms of the GNU General Public License as published by
+# the Free Software Foundation; either version 3, or (at your option)
+# any later version.
+#
+# GNU Radio is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+# GNU General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License
+# along with GNU Radio; see the file COPYING. If not, write to
+# the Free Software Foundation, Inc., 51 Franklin Street,
+# Boston, MA 02110-1301, USA.
+#
+
+For the blow by blow changes for each file, please consult
+http://gnuradio.org/trac/timeline
+
+It's got everything that used to be in here ;)
365 INSTALL
@@ -0,0 +1,365 @@
+Installation Instructions
+*************************
+
+Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005,
+2006, 2007, 2008, 2009 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
+==================
+
+ 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.
+
+ 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 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.
+
+ Running `configure' might take a while. 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, generally using the just-built uninstalled binaries.
+
+ 4. Type `make install' to install the programs and any data files and
+ 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.
+
+ 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
+ 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.
+
+ 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.
+
+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=c99 CFLAGS=-g 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 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.
+
+ 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
+installed the package for one architecture, use `make distclean' before
+reconfiguring for another architecture.
+
+ 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.
+
+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', where PREFIX must be an
+absolute file name.
+
+ 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. 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.
+
+ 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.
+
+ 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.
+
+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
+option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
+
+ 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.
+
+ 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
+
+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).
+
+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
+======================
+
+ `configure' recognizes the following options to control how it
+operates.
+
+`--help'
+`-h'
+ Print a summary of all of the options to `configure', and exit.
+
+`--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.
+
+`--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.
+
+`--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.
+
+`configure' also accepts some other, not widely useful, options. Run
+`configure --help' for more details.
+
Oops, something went wrong.

0 comments on commit e39021f

Please sign in to comment.