1.1 --- a/.hgignore	Sat Mar 03 10:50:33 2012 -0600
     1.2 +++ b/.hgignore	Sat Mar 03 10:54:39 2012 -0600
     1.3 @@ -4,4 +4,8 @@
     1.4  aclocal.m4
     1.5  autom4te.cache*
     1.6  install-sh
     1.7 -missing
     1.8 \ No newline at end of file
     1.9 +missing
    1.10 +depcomp
    1.11 +autoscan.log
    1.12 +configure.scan
    1.13 +*Makefile.in*
    1.14 \ No newline at end of file

     2.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
     2.2 +++ b/COPYING	Sat Mar 03 10:54:39 2012 -0600
     2.3 @@ -0,0 +1,674 @@
     2.4 +                    GNU GENERAL PUBLIC LICENSE
     2.5 +                       Version 3, 29 June 2007
     2.6 +
     2.7 + Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>
     2.8 + Everyone is permitted to copy and distribute verbatim copies
     2.9 + of this license document, but changing it is not allowed.
    2.10 +
    2.11 +                            Preamble
    2.12 +
    2.13 +  The GNU General Public License is a free, copyleft license for
    2.14 +software and other kinds of works.
    2.15 +
    2.16 +  The licenses for most software and other practical works are designed
    2.17 +to take away your freedom to share and change the works.  By contrast,
    2.18 +the GNU General Public License is intended to guarantee your freedom to
    2.19 +share and change all versions of a program--to make sure it remains free
    2.20 +software for all its users.  We, the Free Software Foundation, use the
    2.21 +GNU General Public License for most of our software; it applies also to
    2.22 +any other work released this way by its authors.  You can apply it to
    2.23 +your programs, too.
    2.24 +
    2.25 +  When we speak of free software, we are referring to freedom, not
    2.26 +price.  Our General Public Licenses are designed to make sure that you
    2.27 +have the freedom to distribute copies of free software (and charge for
    2.28 +them if you wish), that you receive source code or can get it if you
    2.29 +want it, that you can change the software or use pieces of it in new
    2.30 +free programs, and that you know you can do these things.
    2.31 +
    2.32 +  To protect your rights, we need to prevent others from denying you
    2.33 +these rights or asking you to surrender the rights.  Therefore, you have
    2.34 +certain responsibilities if you distribute copies of the software, or if
    2.35 +you modify it: responsibilities to respect the freedom of others.
    2.36 +
    2.37 +  For example, if you distribute copies of such a program, whether
    2.38 +gratis or for a fee, you must pass on to the recipients the same
    2.39 +freedoms that you received.  You must make sure that they, too, receive
    2.40 +or can get the source code.  And you must show them these terms so they
    2.41 +know their rights.
    2.42 +
    2.43 +  Developers that use the GNU GPL protect your rights with two steps:
    2.44 +(1) assert copyright on the software, and (2) offer you this License
    2.45 +giving you legal permission to copy, distribute and/or modify it.
    2.46 +
    2.47 +  For the developers' and authors' protection, the GPL clearly explains
    2.48 +that there is no warranty for this free software.  For both users' and
    2.49 +authors' sake, the GPL requires that modified versions be marked as
    2.50 +changed, so that their problems will not be attributed erroneously to
    2.51 +authors of previous versions.
    2.52 +
    2.53 +  Some devices are designed to deny users access to install or run
    2.54 +modified versions of the software inside them, although the manufacturer
    2.55 +can do so.  This is fundamentally incompatible with the aim of
    2.56 +protecting users' freedom to change the software.  The systematic
    2.57 +pattern of such abuse occurs in the area of products for individuals to
    2.58 +use, which is precisely where it is most unacceptable.  Therefore, we
    2.59 +have designed this version of the GPL to prohibit the practice for those
    2.60 +products.  If such problems arise substantially in other domains, we
    2.61 +stand ready to extend this provision to those domains in future versions
    2.62 +of the GPL, as needed to protect the freedom of users.
    2.63 +
    2.64 +  Finally, every program is threatened constantly by software patents.
    2.65 +States should not allow patents to restrict development and use of
    2.66 +software on general-purpose computers, but in those that do, we wish to
    2.67 +avoid the special danger that patents applied to a free program could
    2.68 +make it effectively proprietary.  To prevent this, the GPL assures that
    2.69 +patents cannot be used to render the program non-free.
    2.70 +
    2.71 +  The precise terms and conditions for copying, distribution and
    2.72 +modification follow.
    2.73 +
    2.74 +                       TERMS AND CONDITIONS
    2.75 +
    2.76 +  0. Definitions.
    2.77 +
    2.78 +  "This License" refers to version 3 of the GNU General Public License.
    2.79 +
    2.80 +  "Copyright" also means copyright-like laws that apply to other kinds of
    2.81 +works, such as semiconductor masks.
    2.82 +
    2.83 +  "The Program" refers to any copyrightable work licensed under this
    2.84 +License.  Each licensee is addressed as "you".  "Licensees" and
    2.85 +"recipients" may be individuals or organizations.
    2.86 +
    2.87 +  To "modify" a work means to copy from or adapt all or part of the work
    2.88 +in a fashion requiring copyright permission, other than the making of an
    2.89 +exact copy.  The resulting work is called a "modified version" of the
    2.90 +earlier work or a work "based on" the earlier work.
    2.91 +
    2.92 +  A "covered work" means either the unmodified Program or a work based
    2.93 +on the Program.
    2.94 +
    2.95 +  To "propagate" a work means to do anything with it that, without
    2.96 +permission, would make you directly or secondarily liable for
    2.97 +infringement under applicable copyright law, except executing it on a
    2.98 +computer or modifying a private copy.  Propagation includes copying,
    2.99 +distribution (with or without modification), making available to the
   2.100 +public, and in some countries other activities as well.
   2.101 +
   2.102 +  To "convey" a work means any kind of propagation that enables other
   2.103 +parties to make or receive copies.  Mere interaction with a user through
   2.104 +a computer network, with no transfer of a copy, is not conveying.
   2.105 +
   2.106 +  An interactive user interface displays "Appropriate Legal Notices"
   2.107 +to the extent that it includes a convenient and prominently visible
   2.108 +feature that (1) displays an appropriate copyright notice, and (2)
   2.109 +tells the user that there is no warranty for the work (except to the
   2.110 +extent that warranties are provided), that licensees may convey the
   2.111 +work under this License, and how to view a copy of this License.  If
   2.112 +the interface presents a list of user commands or options, such as a
   2.113 +menu, a prominent item in the list meets this criterion.
   2.114 +
   2.115 +  1. Source Code.
   2.116 +
   2.117 +  The "source code" for a work means the preferred form of the work
   2.118 +for making modifications to it.  "Object code" means any non-source
   2.119 +form of a work.
   2.120 +
   2.121 +  A "Standard Interface" means an interface that either is an official
   2.122 +standard defined by a recognized standards body, or, in the case of
   2.123 +interfaces specified for a particular programming language, one that
   2.124 +is widely used among developers working in that language.
   2.125 +
   2.126 +  The "System Libraries" of an executable work include anything, other
   2.127 +than the work as a whole, that (a) is included in the normal form of
   2.128 +packaging a Major Component, but which is not part of that Major
   2.129 +Component, and (b) serves only to enable use of the work with that
   2.130 +Major Component, or to implement a Standard Interface for which an
   2.131 +implementation is available to the public in source code form.  A
   2.132 +"Major Component", in this context, means a major essential component
   2.133 +(kernel, window system, and so on) of the specific operating system
   2.134 +(if any) on which the executable work runs, or a compiler used to
   2.135 +produce the work, or an object code interpreter used to run it.
   2.136 +
   2.137 +  The "Corresponding Source" for a work in object code form means all
   2.138 +the source code needed to generate, install, and (for an executable
   2.139 +work) run the object code and to modify the work, including scripts to
   2.140 +control those activities.  However, it does not include the work's
   2.141 +System Libraries, or general-purpose tools or generally available free
   2.142 +programs which are used unmodified in performing those activities but
   2.143 +which are not part of the work.  For example, Corresponding Source
   2.144 +includes interface definition files associated with source files for
   2.145 +the work, and the source code for shared libraries and dynamically
   2.146 +linked subprograms that the work is specifically designed to require,
   2.147 +such as by intimate data communication or control flow between those
   2.148 +subprograms and other parts of the work.
   2.149 +
   2.150 +  The Corresponding Source need not include anything that users
   2.151 +can regenerate automatically from other parts of the Corresponding
   2.152 +Source.
   2.153 +
   2.154 +  The Corresponding Source for a work in source code form is that
   2.155 +same work.
   2.156 +
   2.157 +  2. Basic Permissions.
   2.158 +
   2.159 +  All rights granted under this License are granted for the term of
   2.160 +copyright on the Program, and are irrevocable provided the stated
   2.161 +conditions are met.  This License explicitly affirms your unlimited
   2.162 +permission to run the unmodified Program.  The output from running a
   2.163 +covered work is covered by this License only if the output, given its
   2.164 +content, constitutes a covered work.  This License acknowledges your
   2.165 +rights of fair use or other equivalent, as provided by copyright law.
   2.166 +
   2.167 +  You may make, run and propagate covered works that you do not
   2.168 +convey, without conditions so long as your license otherwise remains
   2.169 +in force.  You may convey covered works to others for the sole purpose
   2.170 +of having them make modifications exclusively for you, or provide you
   2.171 +with facilities for running those works, provided that you comply with
   2.172 +the terms of this License in conveying all material for which you do
   2.173 +not control copyright.  Those thus making or running the covered works
   2.174 +for you must do so exclusively on your behalf, under your direction
   2.175 +and control, on terms that prohibit them from making any copies of
   2.176 +your copyrighted material outside their relationship with you.
   2.177 +
   2.178 +  Conveying under any other circumstances is permitted solely under
   2.179 +the conditions stated below.  Sublicensing is not allowed; section 10
   2.180 +makes it unnecessary.
   2.181 +
   2.182 +  3. Protecting Users' Legal Rights From Anti-Circumvention Law.
   2.183 +
   2.184 +  No covered work shall be deemed part of an effective technological
   2.185 +measure under any applicable law fulfilling obligations under article
   2.186 +11 of the WIPO copyright treaty adopted on 20 December 1996, or
   2.187 +similar laws prohibiting or restricting circumvention of such
   2.188 +measures.
   2.189 +
   2.190 +  When you convey a covered work, you waive any legal power to forbid
   2.191 +circumvention of technological measures to the extent such circumvention
   2.192 +is effected by exercising rights under this License with respect to
   2.193 +the covered work, and you disclaim any intention to limit operation or
   2.194 +modification of the work as a means of enforcing, against the work's
   2.195 +users, your or third parties' legal rights to forbid circumvention of
   2.196 +technological measures.
   2.197 +
   2.198 +  4. Conveying Verbatim Copies.
   2.199 +
   2.200 +  You may convey verbatim copies of the Program's source code as you
   2.201 +receive it, in any medium, provided that you conspicuously and
   2.202 +appropriately publish on each copy an appropriate copyright notice;
   2.203 +keep intact all notices stating that this License and any
   2.204 +non-permissive terms added in accord with section 7 apply to the code;
   2.205 +keep intact all notices of the absence of any warranty; and give all
   2.206 +recipients a copy of this License along with the Program.
   2.207 +
   2.208 +  You may charge any price or no price for each copy that you convey,
   2.209 +and you may offer support or warranty protection for a fee.
   2.210 +
   2.211 +  5. Conveying Modified Source Versions.
   2.212 +
   2.213 +  You may convey a work based on the Program, or the modifications to
   2.214 +produce it from the Program, in the form of source code under the
   2.215 +terms of section 4, provided that you also meet all of these conditions:
   2.216 +
   2.217 +    a) The work must carry prominent notices stating that you modified
   2.218 +    it, and giving a relevant date.
   2.219 +
   2.220 +    b) The work must carry prominent notices stating that it is
   2.221 +    released under this License and any conditions added under section
   2.222 +    7.  This requirement modifies the requirement in section 4 to
   2.223 +    "keep intact all notices".
   2.224 +
   2.225 +    c) You must license the entire work, as a whole, under this
   2.226 +    License to anyone who comes into possession of a copy.  This
   2.227 +    License will therefore apply, along with any applicable section 7
   2.228 +    additional terms, to the whole of the work, and all its parts,
   2.229 +    regardless of how they are packaged.  This License gives no
   2.230 +    permission to license the work in any other way, but it does not
   2.231 +    invalidate such permission if you have separately received it.
   2.232 +
   2.233 +    d) If the work has interactive user interfaces, each must display
   2.234 +    Appropriate Legal Notices; however, if the Program has interactive
   2.235 +    interfaces that do not display Appropriate Legal Notices, your
   2.236 +    work need not make them do so.
   2.237 +
   2.238 +  A compilation of a covered work with other separate and independent
   2.239 +works, which are not by their nature extensions of the covered work,
   2.240 +and which are not combined with it such as to form a larger program,
   2.241 +in or on a volume of a storage or distribution medium, is called an
   2.242 +"aggregate" if the compilation and its resulting copyright are not
   2.243 +used to limit the access or legal rights of the compilation's users
   2.244 +beyond what the individual works permit.  Inclusion of a covered work
   2.245 +in an aggregate does not cause this License to apply to the other
   2.246 +parts of the aggregate.
   2.247 +
   2.248 +  6. Conveying Non-Source Forms.
   2.249 +
   2.250 +  You may convey a covered work in object code form under the terms
   2.251 +of sections 4 and 5, provided that you also convey the
   2.252 +machine-readable Corresponding Source under the terms of this License,
   2.253 +in one of these ways:
   2.254 +
   2.255 +    a) Convey the object code in, or embodied in, a physical product
   2.256 +    (including a physical distribution medium), accompanied by the
   2.257 +    Corresponding Source fixed on a durable physical medium
   2.258 +    customarily used for software interchange.
   2.259 +
   2.260 +    b) Convey the object code in, or embodied in, a physical product
   2.261 +    (including a physical distribution medium), accompanied by a
   2.262 +    written offer, valid for at least three years and valid for as
   2.263 +    long as you offer spare parts or customer support for that product
   2.264 +    model, to give anyone who possesses the object code either (1) a
   2.265 +    copy of the Corresponding Source for all the software in the
   2.266 +    product that is covered by this License, on a durable physical
   2.267 +    medium customarily used for software interchange, for a price no
   2.268 +    more than your reasonable cost of physically performing this
   2.269 +    conveying of source, or (2) access to copy the
   2.270 +    Corresponding Source from a network server at no charge.
   2.271 +
   2.272 +    c) Convey individual copies of the object code with a copy of the
   2.273 +    written offer to provide the Corresponding Source.  This
   2.274 +    alternative is allowed only occasionally and noncommercially, and
   2.275 +    only if you received the object code with such an offer, in accord
   2.276 +    with subsection 6b.
   2.277 +
   2.278 +    d) Convey the object code by offering access from a designated
   2.279 +    place (gratis or for a charge), and offer equivalent access to the
   2.280 +    Corresponding Source in the same way through the same place at no
   2.281 +    further charge.  You need not require recipients to copy the
   2.282 +    Corresponding Source along with the object code.  If the place to
   2.283 +    copy the object code is a network server, the Corresponding Source
   2.284 +    may be on a different server (operated by you or a third party)
   2.285 +    that supports equivalent copying facilities, provided you maintain
   2.286 +    clear directions next to the object code saying where to find the
   2.287 +    Corresponding Source.  Regardless of what server hosts the
   2.288 +    Corresponding Source, you remain obligated to ensure that it is
   2.289 +    available for as long as needed to satisfy these requirements.
   2.290 +
   2.291 +    e) Convey the object code using peer-to-peer transmission, provided
   2.292 +    you inform other peers where the object code and Corresponding
   2.293 +    Source of the work are being offered to the general public at no
   2.294 +    charge under subsection 6d.
   2.295 +
   2.296 +  A separable portion of the object code, whose source code is excluded
   2.297 +from the Corresponding Source as a System Library, need not be
   2.298 +included in conveying the object code work.
   2.299 +
   2.300 +  A "User Product" is either (1) a "consumer product", which means any
   2.301 +tangible personal property which is normally used for personal, family,
   2.302 +or household purposes, or (2) anything designed or sold for incorporation
   2.303 +into a dwelling.  In determining whether a product is a consumer product,
   2.304 +doubtful cases shall be resolved in favor of coverage.  For a particular
   2.305 +product received by a particular user, "normally used" refers to a
   2.306 +typical or common use of that class of product, regardless of the status
   2.307 +of the particular user or of the way in which the particular user
   2.308 +actually uses, or expects or is expected to use, the product.  A product
   2.309 +is a consumer product regardless of whether the product has substantial
   2.310 +commercial, industrial or non-consumer uses, unless such uses represent
   2.311 +the only significant mode of use of the product.
   2.312 +
   2.313 +  "Installation Information" for a User Product means any methods,
   2.314 +procedures, authorization keys, or other information required to install
   2.315 +and execute modified versions of a covered work in that User Product from
   2.316 +a modified version of its Corresponding Source.  The information must
   2.317 +suffice to ensure that the continued functioning of the modified object
   2.318 +code is in no case prevented or interfered with solely because
   2.319 +modification has been made.
   2.320 +
   2.321 +  If you convey an object code work under this section in, or with, or
   2.322 +specifically for use in, a User Product, and the conveying occurs as
   2.323 +part of a transaction in which the right of possession and use of the
   2.324 +User Product is transferred to the recipient in perpetuity or for a
   2.325 +fixed term (regardless of how the transaction is characterized), the
   2.326 +Corresponding Source conveyed under this section must be accompanied
   2.327 +by the Installation Information.  But this requirement does not apply
   2.328 +if neither you nor any third party retains the ability to install
   2.329 +modified object code on the User Product (for example, the work has
   2.330 +been installed in ROM).
   2.331 +
   2.332 +  The requirement to provide Installation Information does not include a
   2.333 +requirement to continue to provide support service, warranty, or updates
   2.334 +for a work that has been modified or installed by the recipient, or for
   2.335 +the User Product in which it has been modified or installed.  Access to a
   2.336 +network may be denied when the modification itself materially and
   2.337 +adversely affects the operation of the network or violates the rules and
   2.338 +protocols for communication across the network.
   2.339 +
   2.340 +  Corresponding Source conveyed, and Installation Information provided,
   2.341 +in accord with this section must be in a format that is publicly
   2.342 +documented (and with an implementation available to the public in
   2.343 +source code form), and must require no special password or key for
   2.344 +unpacking, reading or copying.
   2.345 +
   2.346 +  7. Additional Terms.
   2.347 +
   2.348 +  "Additional permissions" are terms that supplement the terms of this
   2.349 +License by making exceptions from one or more of its conditions.
   2.350 +Additional permissions that are applicable to the entire Program shall
   2.351 +be treated as though they were included in this License, to the extent
   2.352 +that they are valid under applicable law.  If additional permissions
   2.353 +apply only to part of the Program, that part may be used separately
   2.354 +under those permissions, but the entire Program remains governed by
   2.355 +this License without regard to the additional permissions.
   2.356 +
   2.357 +  When you convey a copy of a covered work, you may at your option
   2.358 +remove any additional permissions from that copy, or from any part of
   2.359 +it.  (Additional permissions may be written to require their own
   2.360 +removal in certain cases when you modify the work.)  You may place
   2.361 +additional permissions on material, added by you to a covered work,
   2.362 +for which you have or can give appropriate copyright permission.
   2.363 +
   2.364 +  Notwithstanding any other provision of this License, for material you
   2.365 +add to a covered work, you may (if authorized by the copyright holders of
   2.366 +that material) supplement the terms of this License with terms:
   2.367 +
   2.368 +    a) Disclaiming warranty or limiting liability differently from the
   2.369 +    terms of sections 15 and 16 of this License; or
   2.370 +
   2.371 +    b) Requiring preservation of specified reasonable legal notices or
   2.372 +    author attributions in that material or in the Appropriate Legal
   2.373 +    Notices displayed by works containing it; or
   2.374 +
   2.375 +    c) Prohibiting misrepresentation of the origin of that material, or
   2.376 +    requiring that modified versions of such material be marked in
   2.377 +    reasonable ways as different from the original version; or
   2.378 +
   2.379 +    d) Limiting the use for publicity purposes of names of licensors or
   2.380 +    authors of the material; or
   2.381 +
   2.382 +    e) Declining to grant rights under trademark law for use of some
   2.383 +    trade names, trademarks, or service marks; or
   2.384 +
   2.385 +    f) Requiring indemnification of licensors and authors of that
   2.386 +    material by anyone who conveys the material (or modified versions of
   2.387 +    it) with contractual assumptions of liability to the recipient, for
   2.388 +    any liability that these contractual assumptions directly impose on
   2.389 +    those licensors and authors.
   2.390 +
   2.391 +  All other non-permissive additional terms are considered "further
   2.392 +restrictions" within the meaning of section 10.  If the Program as you
   2.393 +received it, or any part of it, contains a notice stating that it is
   2.394 +governed by this License along with a term that is a further
   2.395 +restriction, you may remove that term.  If a license document contains
   2.396 +a further restriction but permits relicensing or conveying under this
   2.397 +License, you may add to a covered work material governed by the terms
   2.398 +of that license document, provided that the further restriction does
   2.399 +not survive such relicensing or conveying.
   2.400 +
   2.401 +  If you add terms to a covered work in accord with this section, you
   2.402 +must place, in the relevant source files, a statement of the
   2.403 +additional terms that apply to those files, or a notice indicating
   2.404 +where to find the applicable terms.
   2.405 +
   2.406 +  Additional terms, permissive or non-permissive, may be stated in the
   2.407 +form of a separately written license, or stated as exceptions;
   2.408 +the above requirements apply either way.
   2.409 +
   2.410 +  8. Termination.
   2.411 +
   2.412 +  You may not propagate or modify a covered work except as expressly
   2.413 +provided under this License.  Any attempt otherwise to propagate or
   2.414 +modify it is void, and will automatically terminate your rights under
   2.415 +this License (including any patent licenses granted under the third
   2.416 +paragraph of section 11).
   2.417 +
   2.418 +  However, if you cease all violation of this License, then your
   2.419 +license from a particular copyright holder is reinstated (a)
   2.420 +provisionally, unless and until the copyright holder explicitly and
   2.421 +finally terminates your license, and (b) permanently, if the copyright
   2.422 +holder fails to notify you of the violation by some reasonable means
   2.423 +prior to 60 days after the cessation.
   2.424 +
   2.425 +  Moreover, your license from a particular copyright holder is
   2.426 +reinstated permanently if the copyright holder notifies you of the
   2.427 +violation by some reasonable means, this is the first time you have
   2.428 +received notice of violation of this License (for any work) from that
   2.429 +copyright holder, and you cure the violation prior to 30 days after
   2.430 +your receipt of the notice.
   2.431 +
   2.432 +  Termination of your rights under this section does not terminate the
   2.433 +licenses of parties who have received copies or rights from you under
   2.434 +this License.  If your rights have been terminated and not permanently
   2.435 +reinstated, you do not qualify to receive new licenses for the same
   2.436 +material under section 10.
   2.437 +
   2.438 +  9. Acceptance Not Required for Having Copies.
   2.439 +
   2.440 +  You are not required to accept this License in order to receive or
   2.441 +run a copy of the Program.  Ancillary propagation of a covered work
   2.442 +occurring solely as a consequence of using peer-to-peer transmission
   2.443 +to receive a copy likewise does not require acceptance.  However,
   2.444 +nothing other than this License grants you permission to propagate or
   2.445 +modify any covered work.  These actions infringe copyright if you do
   2.446 +not accept this License.  Therefore, by modifying or propagating a
   2.447 +covered work, you indicate your acceptance of this License to do so.
   2.448 +
   2.449 +  10. Automatic Licensing of Downstream Recipients.
   2.450 +
   2.451 +  Each time you convey a covered work, the recipient automatically
   2.452 +receives a license from the original licensors, to run, modify and
   2.453 +propagate that work, subject to this License.  You are not responsible
   2.454 +for enforcing compliance by third parties with this License.
   2.455 +
   2.456 +  An "entity transaction" is a transaction transferring control of an
   2.457 +organization, or substantially all assets of one, or subdividing an
   2.458 +organization, or merging organizations.  If propagation of a covered
   2.459 +work results from an entity transaction, each party to that
   2.460 +transaction who receives a copy of the work also receives whatever
   2.461 +licenses to the work the party's predecessor in interest had or could
   2.462 +give under the previous paragraph, plus a right to possession of the
   2.463 +Corresponding Source of the work from the predecessor in interest, if
   2.464 +the predecessor has it or can get it with reasonable efforts.
   2.465 +
   2.466 +  You may not impose any further restrictions on the exercise of the
   2.467 +rights granted or affirmed under this License.  For example, you may
   2.468 +not impose a license fee, royalty, or other charge for exercise of
   2.469 +rights granted under this License, and you may not initiate litigation
   2.470 +(including a cross-claim or counterclaim in a lawsuit) alleging that
   2.471 +any patent claim is infringed by making, using, selling, offering for
   2.472 +sale, or importing the Program or any portion of it.
   2.473 +
   2.474 +  11. Patents.
   2.475 +
   2.476 +  A "contributor" is a copyright holder who authorizes use under this
   2.477 +License of the Program or a work on which the Program is based.  The
   2.478 +work thus licensed is called the contributor's "contributor version".
   2.479 +
   2.480 +  A contributor's "essential patent claims" are all patent claims
   2.481 +owned or controlled by the contributor, whether already acquired or
   2.482 +hereafter acquired, that would be infringed by some manner, permitted
   2.483 +by this License, of making, using, or selling its contributor version,
   2.484 +but do not include claims that would be infringed only as a
   2.485 +consequence of further modification of the contributor version.  For
   2.486 +purposes of this definition, "control" includes the right to grant
   2.487 +patent sublicenses in a manner consistent with the requirements of
   2.488 +this License.
   2.489 +
   2.490 +  Each contributor grants you a non-exclusive, worldwide, royalty-free
   2.491 +patent license under the contributor's essential patent claims, to
   2.492 +make, use, sell, offer for sale, import and otherwise run, modify and
   2.493 +propagate the contents of its contributor version.
   2.494 +
   2.495 +  In the following three paragraphs, a "patent license" is any express
   2.496 +agreement or commitment, however denominated, not to enforce a patent
   2.497 +(such as an express permission to practice a patent or covenant not to
   2.498 +sue for patent infringement).  To "grant" such a patent license to a
   2.499 +party means to make such an agreement or commitment not to enforce a
   2.500 +patent against the party.
   2.501 +
   2.502 +  If you convey a covered work, knowingly relying on a patent license,
   2.503 +and the Corresponding Source of the work is not available for anyone
   2.504 +to copy, free of charge and under the terms of this License, through a
   2.505 +publicly available network server or other readily accessible means,
   2.506 +then you must either (1) cause the Corresponding Source to be so
   2.507 +available, or (2) arrange to deprive yourself of the benefit of the
   2.508 +patent license for this particular work, or (3) arrange, in a manner
   2.509 +consistent with the requirements of this License, to extend the patent
   2.510 +license to downstream recipients.  "Knowingly relying" means you have
   2.511 +actual knowledge that, but for the patent license, your conveying the
   2.512 +covered work in a country, or your recipient's use of the covered work
   2.513 +in a country, would infringe one or more identifiable patents in that
   2.514 +country that you have reason to believe are valid.
   2.515 +
   2.516 +  If, pursuant to or in connection with a single transaction or
   2.517 +arrangement, you convey, or propagate by procuring conveyance of, a
   2.518 +covered work, and grant a patent license to some of the parties
   2.519 +receiving the covered work authorizing them to use, propagate, modify
   2.520 +or convey a specific copy of the covered work, then the patent license
   2.521 +you grant is automatically extended to all recipients of the covered
   2.522 +work and works based on it.
   2.523 +
   2.524 +  A patent license is "discriminatory" if it does not include within
   2.525 +the scope of its coverage, prohibits the exercise of, or is
   2.526 +conditioned on the non-exercise of one or more of the rights that are
   2.527 +specifically granted under this License.  You may not convey a covered
   2.528 +work if you are a party to an arrangement with a third party that is
   2.529 +in the business of distributing software, under which you make payment
   2.530 +to the third party based on the extent of your activity of conveying
   2.531 +the work, and under which the third party grants, to any of the
   2.532 +parties who would receive the covered work from you, a discriminatory
   2.533 +patent license (a) in connection with copies of the covered work
   2.534 +conveyed by you (or copies made from those copies), or (b) primarily
   2.535 +for and in connection with specific products or compilations that
   2.536 +contain the covered work, unless you entered into that arrangement,
   2.537 +or that patent license was granted, prior to 28 March 2007.
   2.538 +
   2.539 +  Nothing in this License shall be construed as excluding or limiting
   2.540 +any implied license or other defenses to infringement that may
   2.541 +otherwise be available to you under applicable patent law.
   2.542 +
   2.543 +  12. No Surrender of Others' Freedom.
   2.544 +
   2.545 +  If conditions are imposed on you (whether by court order, agreement or
   2.546 +otherwise) that contradict the conditions of this License, they do not
   2.547 +excuse you from the conditions of this License.  If you cannot convey a
   2.548 +covered work so as to satisfy simultaneously your obligations under this
   2.549 +License and any other pertinent obligations, then as a consequence you may
   2.550 +not convey it at all.  For example, if you agree to terms that obligate you
   2.551 +to collect a royalty for further conveying from those to whom you convey
   2.552 +the Program, the only way you could satisfy both those terms and this
   2.553 +License would be to refrain entirely from conveying the Program.
   2.554 +
   2.555 +  13. Use with the GNU Affero General Public License.
   2.556 +
   2.557 +  Notwithstanding any other provision of this License, you have
   2.558 +permission to link or combine any covered work with a work licensed
   2.559 +under version 3 of the GNU Affero General Public License into a single
   2.560 +combined work, and to convey the resulting work.  The terms of this
   2.561 +License will continue to apply to the part which is the covered work,
   2.562 +but the special requirements of the GNU Affero General Public License,
   2.563 +section 13, concerning interaction through a network will apply to the
   2.564 +combination as such.
   2.565 +
   2.566 +  14. Revised Versions of this License.
   2.567 +
   2.568 +  The Free Software Foundation may publish revised and/or new versions of
   2.569 +the GNU General Public License from time to time.  Such new versions will
   2.570 +be similar in spirit to the present version, but may differ in detail to
   2.571 +address new problems or concerns.
   2.572 +
   2.573 +  Each version is given a distinguishing version number.  If the
   2.574 +Program specifies that a certain numbered version of the GNU General
   2.575 +Public License "or any later version" applies to it, you have the
   2.576 +option of following the terms and conditions either of that numbered
   2.577 +version or of any later version published by the Free Software
   2.578 +Foundation.  If the Program does not specify a version number of the
   2.579 +GNU General Public License, you may choose any version ever published
   2.580 +by the Free Software Foundation.
   2.581 +
   2.582 +  If the Program specifies that a proxy can decide which future
   2.583 +versions of the GNU General Public License can be used, that proxy's
   2.584 +public statement of acceptance of a version permanently authorizes you
   2.585 +to choose that version for the Program.
   2.586 +
   2.587 +  Later license versions may give you additional or different
   2.588 +permissions.  However, no additional obligations are imposed on any
   2.589 +author or copyright holder as a result of your choosing to follow a
   2.590 +later version.
   2.591 +
   2.592 +  15. Disclaimer of Warranty.
   2.593 +
   2.594 +  THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
   2.595 +APPLICABLE LAW.  EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
   2.596 +HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
   2.597 +OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
   2.598 +THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
   2.599 +PURPOSE.  THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
   2.600 +IS WITH YOU.  SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
   2.601 +ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
   2.602 +
   2.603 +  16. Limitation of Liability.
   2.604 +
   2.605 +  IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
   2.606 +WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
   2.607 +THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
   2.608 +GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
   2.609 +USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
   2.610 +DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
   2.611 +PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
   2.612 +EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
   2.613 +SUCH DAMAGES.
   2.614 +
   2.615 +  17. Interpretation of Sections 15 and 16.
   2.616 +
   2.617 +  If the disclaimer of warranty and limitation of liability provided
   2.618 +above cannot be given local legal effect according to their terms,
   2.619 +reviewing courts shall apply local law that most closely approximates
   2.620 +an absolute waiver of all civil liability in connection with the
   2.621 +Program, unless a warranty or assumption of liability accompanies a
   2.622 +copy of the Program in return for a fee.
   2.623 +
   2.624 +                     END OF TERMS AND CONDITIONS
   2.625 +
   2.626 +            How to Apply These Terms to Your New Programs
   2.627 +
   2.628 +  If you develop a new program, and you want it to be of the greatest
   2.629 +possible use to the public, the best way to achieve this is to make it
   2.630 +free software which everyone can redistribute and change under these terms.
   2.631 +
   2.632 +  To do so, attach the following notices to the program.  It is safest
   2.633 +to attach them to the start of each source file to most effectively
   2.634 +state the exclusion of warranty; and each file should have at least
   2.635 +the "copyright" line and a pointer to where the full notice is found.
   2.636 +
   2.637 +    <one line to give the program's name and a brief idea of what it does.>
   2.638 +    Copyright (C) <year>  <name of author>
   2.639 +
   2.640 +    This program is free software: you can redistribute it and/or modify
   2.641 +    it under the terms of the GNU General Public License as published by
   2.642 +    the Free Software Foundation, either version 3 of the License, or
   2.643 +    (at your option) any later version.
   2.644 +
   2.645 +    This program is distributed in the hope that it will be useful,
   2.646 +    but WITHOUT ANY WARRANTY; without even the implied warranty of
   2.647 +    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
   2.648 +    GNU General Public License for more details.
   2.649 +
   2.650 +    You should have received a copy of the GNU General Public License
   2.651 +    along with this program.  If not, see <http://www.gnu.org/licenses/>.
   2.652 +
   2.653 +Also add information on how to contact you by electronic and paper mail.
   2.654 +
   2.655 +  If the program does terminal interaction, make it output a short
   2.656 +notice like this when it starts in an interactive mode:
   2.657 +
   2.658 +    <program>  Copyright (C) <year>  <name of author>
   2.659 +    This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
   2.660 +    This is free software, and you are welcome to redistribute it
   2.661 +    under certain conditions; type `show c' for details.
   2.662 +
   2.663 +The hypothetical commands `show w' and `show c' should show the appropriate
   2.664 +parts of the General Public License.  Of course, your program's commands
   2.665 +might be different; for a GUI interface, you would use an "about box".
   2.666 +
   2.667 +  You should also get your employer (if you work as a programmer) or school,
   2.668 +if any, to sign a "copyright disclaimer" for the program, if necessary.
   2.669 +For more information on this, and how to apply and follow the GNU GPL, see
   2.670 +<http://www.gnu.org/licenses/>.
   2.671 +
   2.672 +  The GNU General Public License does not permit incorporating your program
   2.673 +into proprietary programs.  If your program is a subroutine library, you
   2.674 +may consider it more useful to permit linking proprietary applications with
   2.675 +the library.  If this is what you want to do, use the GNU Lesser General
   2.676 +Public License instead of this License.  But first, please read
   2.677 +<http://www.gnu.org/philosophy/why-not-lgpl.html>.

     3.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
     3.2 +++ b/INSTALL	Sat Mar 03 10:54:39 2012 -0600
     3.3 @@ -0,0 +1,365 @@
     3.4 +Installation Instructions
     3.5 +*************************
     3.6 +
     3.7 +Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005,
     3.8 +2006, 2007, 2008, 2009 Free Software Foundation, Inc.
     3.9 +
    3.10 +   Copying and distribution of this file, with or without modification,
    3.11 +are permitted in any medium without royalty provided the copyright
    3.12 +notice and this notice are preserved.  This file is offered as-is,
    3.13 +without warranty of any kind.
    3.14 +
    3.15 +Basic Installation
    3.16 +==================
    3.17 +
    3.18 +   Briefly, the shell commands `./configure; make; make install' should
    3.19 +configure, build, and install this package.  The following
    3.20 +more-detailed instructions are generic; see the `README' file for
    3.21 +instructions specific to this package.  Some packages provide this
    3.22 +`INSTALL' file but do not implement all of the features documented
    3.23 +below.  The lack of an optional feature in a given package is not
    3.24 +necessarily a bug.  More recommendations for GNU packages can be found
    3.25 +in *note Makefile Conventions: (standards)Makefile Conventions.
    3.26 +
    3.27 +   The `configure' shell script attempts to guess correct values for
    3.28 +various system-dependent variables used during compilation.  It uses
    3.29 +those values to create a `Makefile' in each directory of the package.
    3.30 +It may also create one or more `.h' files containing system-dependent
    3.31 +definitions.  Finally, it creates a shell script `config.status' that
    3.32 +you can run in the future to recreate the current configuration, and a
    3.33 +file `config.log' containing compiler output (useful mainly for
    3.34 +debugging `configure').
    3.35 +
    3.36 +   It can also use an optional file (typically called `config.cache'
    3.37 +and enabled with `--cache-file=config.cache' or simply `-C') that saves
    3.38 +the results of its tests to speed up reconfiguring.  Caching is
    3.39 +disabled by default to prevent problems with accidental use of stale
    3.40 +cache files.
    3.41 +
    3.42 +   If you need to do unusual things to compile the package, please try
    3.43 +to figure out how `configure' could check whether to do them, and mail
    3.44 +diffs or instructions to the address given in the `README' so they can
    3.45 +be considered for the next release.  If you are using the cache, and at
    3.46 +some point `config.cache' contains results you don't want to keep, you
    3.47 +may remove or edit it.
    3.48 +
    3.49 +   The file `configure.ac' (or `configure.in') is used to create
    3.50 +`configure' by a program called `autoconf'.  You need `configure.ac' if
    3.51 +you want to change it or regenerate `configure' using a newer version
    3.52 +of `autoconf'.
    3.53 +
    3.54 +   The simplest way to compile this package is:
    3.55 +
    3.56 +  1. `cd' to the directory containing the package's source code and type
    3.57 +     `./configure' to configure the package for your system.
    3.58 +
    3.59 +     Running `configure' might take a while.  While running, it prints
    3.60 +     some messages telling which features it is checking for.
    3.61 +
    3.62 +  2. Type `make' to compile the package.
    3.63 +
    3.64 +  3. Optionally, type `make check' to run any self-tests that come with
    3.65 +     the package, generally using the just-built uninstalled binaries.
    3.66 +
    3.67 +  4. Type `make install' to install the programs and any data files and
    3.68 +     documentation.  When installing into a prefix owned by root, it is
    3.69 +     recommended that the package be configured and built as a regular
    3.70 +     user, and only the `make install' phase executed with root
    3.71 +     privileges.
    3.72 +
    3.73 +  5. Optionally, type `make installcheck' to repeat any self-tests, but
    3.74 +     this time using the binaries in their final installed location.
    3.75 +     This target does not install anything.  Running this target as a
    3.76 +     regular user, particularly if the prior `make install' required
    3.77 +     root privileges, verifies that the installation completed
    3.78 +     correctly.
    3.79 +
    3.80 +  6. You can remove the program binaries and object files from the
    3.81 +     source code directory by typing `make clean'.  To also remove the
    3.82 +     files that `configure' created (so you can compile the package for
    3.83 +     a different kind of computer), type `make distclean'.  There is
    3.84 +     also a `make maintainer-clean' target, but that is intended mainly
    3.85 +     for the package's developers.  If you use it, you may have to get
    3.86 +     all sorts of other programs in order to regenerate files that came
    3.87 +     with the distribution.
    3.88 +
    3.89 +  7. Often, you can also type `make uninstall' to remove the installed
    3.90 +     files again.  In practice, not all packages have tested that
    3.91 +     uninstallation works correctly, even though it is required by the
    3.92 +     GNU Coding Standards.
    3.93 +
    3.94 +  8. Some packages, particularly those that use Automake, provide `make
    3.95 +     distcheck', which can by used by developers to test that all other
    3.96 +     targets like `make install' and `make uninstall' work correctly.
    3.97 +     This target is generally not run by end users.
    3.98 +
    3.99 +Compilers and Options
   3.100 +=====================
   3.101 +
   3.102 +   Some systems require unusual options for compilation or linking that
   3.103 +the `configure' script does not know about.  Run `./configure --help'
   3.104 +for details on some of the pertinent environment variables.
   3.105 +
   3.106 +   You can give `configure' initial values for configuration parameters
   3.107 +by setting variables in the command line or in the environment.  Here
   3.108 +is an example:
   3.109 +
   3.110 +     ./configure CC=c99 CFLAGS=-g LIBS=-lposix
   3.111 +
   3.112 +   *Note Defining Variables::, for more details.
   3.113 +
   3.114 +Compiling For Multiple Architectures
   3.115 +====================================
   3.116 +
   3.117 +   You can compile the package for more than one kind of computer at the
   3.118 +same time, by placing the object files for each architecture in their
   3.119 +own directory.  To do this, you can use GNU `make'.  `cd' to the
   3.120 +directory where you want the object files and executables to go and run
   3.121 +the `configure' script.  `configure' automatically checks for the
   3.122 +source code in the directory that `configure' is in and in `..'.  This
   3.123 +is known as a "VPATH" build.
   3.124 +
   3.125 +   With a non-GNU `make', it is safer to compile the package for one
   3.126 +architecture at a time in the source code directory.  After you have
   3.127 +installed the package for one architecture, use `make distclean' before
   3.128 +reconfiguring for another architecture.
   3.129 +
   3.130 +   On MacOS X 10.5 and later systems, you can create libraries and
   3.131 +executables that work on multiple system types--known as "fat" or
   3.132 +"universal" binaries--by specifying multiple `-arch' options to the
   3.133 +compiler but only a single `-arch' option to the preprocessor.  Like
   3.134 +this:
   3.135 +
   3.136 +     ./configure CC="gcc -arch i386 -arch x86_64 -arch ppc -arch ppc64" \
   3.137 +                 CXX="g++ -arch i386 -arch x86_64 -arch ppc -arch ppc64" \
   3.138 +                 CPP="gcc -E" CXXCPP="g++ -E"
   3.139 +
   3.140 +   This is not guaranteed to produce working output in all cases, you
   3.141 +may have to build one architecture at a time and combine the results
   3.142 +using the `lipo' tool if you have problems.
   3.143 +
   3.144 +Installation Names
   3.145 +==================
   3.146 +
   3.147 +   By default, `make install' installs the package's commands under
   3.148 +`/usr/local/bin', include files under `/usr/local/include', etc.  You
   3.149 +can specify an installation prefix other than `/usr/local' by giving
   3.150 +`configure' the option `--prefix=PREFIX', where PREFIX must be an
   3.151 +absolute file name.
   3.152 +
   3.153 +   You can specify separate installation prefixes for
   3.154 +architecture-specific files and architecture-independent files.  If you
   3.155 +pass the option `--exec-prefix=PREFIX' to `configure', the package uses
   3.156 +PREFIX as the prefix for installing programs and libraries.
   3.157 +Documentation and other data files still use the regular prefix.
   3.158 +
   3.159 +   In addition, if you use an unusual directory layout you can give
   3.160 +options like `--bindir=DIR' to specify different values for particular
   3.161 +kinds of files.  Run `configure --help' for a list of the directories
   3.162 +you can set and what kinds of files go in them.  In general, the
   3.163 +default for these options is expressed in terms of `${prefix}', so that
   3.164 +specifying just `--prefix' will affect all of the other directory
   3.165 +specifications that were not explicitly provided.
   3.166 +
   3.167 +   The most portable way to affect installation locations is to pass the
   3.168 +correct locations to `configure'; however, many packages provide one or
   3.169 +both of the following shortcuts of passing variable assignments to the
   3.170 +`make install' command line to change installation locations without
   3.171 +having to reconfigure or recompile.
   3.172 +
   3.173 +   The first method involves providing an override variable for each
   3.174 +affected directory.  For example, `make install
   3.175 +prefix=/alternate/directory' will choose an alternate location for all
   3.176 +directory configuration variables that were expressed in terms of
   3.177 +`${prefix}'.  Any directories that were specified during `configure',
   3.178 +but not in terms of `${prefix}', must each be overridden at install
   3.179 +time for the entire installation to be relocated.  The approach of
   3.180 +makefile variable overrides for each directory variable is required by
   3.181 +the GNU Coding Standards, and ideally causes no recompilation.
   3.182 +However, some platforms have known limitations with the semantics of
   3.183 +shared libraries that end up requiring recompilation when using this
   3.184 +method, particularly noticeable in packages that use GNU Libtool.
   3.185 +
   3.186 +   The second method involves providing the `DESTDIR' variable.  For
   3.187 +example, `make install DESTDIR=/alternate/directory' will prepend
   3.188 +`/alternate/directory' before all installation names.  The approach of
   3.189 +`DESTDIR' overrides is not required by the GNU Coding Standards, and
   3.190 +does not work on platforms that have drive letters.  On the other hand,
   3.191 +it does better at avoiding recompilation issues, and works well even
   3.192 +when some directory options were not specified in terms of `${prefix}'
   3.193 +at `configure' time.
   3.194 +
   3.195 +Optional Features
   3.196 +=================
   3.197 +
   3.198 +   If the package supports it, you can cause programs to be installed
   3.199 +with an extra prefix or suffix on their names by giving `configure' the
   3.200 +option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
   3.201 +
   3.202 +   Some packages pay attention to `--enable-FEATURE' options to
   3.203 +`configure', where FEATURE indicates an optional part of the package.
   3.204 +They may also pay attention to `--with-PACKAGE' options, where PACKAGE
   3.205 +is something like `gnu-as' or `x' (for the X Window System).  The
   3.206 +`README' should mention any `--enable-' and `--with-' options that the
   3.207 +package recognizes.
   3.208 +
   3.209 +   For packages that use the X Window System, `configure' can usually
   3.210 +find the X include and library files automatically, but if it doesn't,
   3.211 +you can use the `configure' options `--x-includes=DIR' and
   3.212 +`--x-libraries=DIR' to specify their locations.
   3.213 +
   3.214 +   Some packages offer the ability to configure how verbose the
   3.215 +execution of `make' will be.  For these packages, running `./configure
   3.216 +--enable-silent-rules' sets the default to minimal output, which can be
   3.217 +overridden with `make V=1'; while running `./configure
   3.218 +--disable-silent-rules' sets the default to verbose, which can be
   3.219 +overridden with `make V=0'.
   3.220 +
   3.221 +Particular systems
   3.222 +==================
   3.223 +
   3.224 +   On HP-UX, the default C compiler is not ANSI C compatible.  If GNU
   3.225 +CC is not installed, it is recommended to use the following options in
   3.226 +order to use an ANSI C compiler:
   3.227 +
   3.228 +     ./configure CC="cc -Ae -D_XOPEN_SOURCE=500"
   3.229 +
   3.230 +and if that doesn't work, install pre-built binaries of GCC for HP-UX.
   3.231 +
   3.232 +   On OSF/1 a.k.a. Tru64, some versions of the default C compiler cannot
   3.233 +parse its `<wchar.h>' header file.  The option `-nodtk' can be used as
   3.234 +a workaround.  If GNU CC is not installed, it is therefore recommended
   3.235 +to try
   3.236 +
   3.237 +     ./configure CC="cc"
   3.238 +
   3.239 +and if that doesn't work, try
   3.240 +
   3.241 +     ./configure CC="cc -nodtk"
   3.242 +
   3.243 +   On Solaris, don't put `/usr/ucb' early in your `PATH'.  This
   3.244 +directory contains several dysfunctional programs; working variants of
   3.245 +these programs are available in `/usr/bin'.  So, if you need `/usr/ucb'
   3.246 +in your `PATH', put it _after_ `/usr/bin'.
   3.247 +
   3.248 +   On Haiku, software installed for all users goes in `/boot/common',
   3.249 +not `/usr/local'.  It is recommended to use the following options:
   3.250 +
   3.251 +     ./configure --prefix=/boot/common
   3.252 +
   3.253 +Specifying the System Type
   3.254 +==========================
   3.255 +
   3.256 +   There may be some features `configure' cannot figure out
   3.257 +automatically, but needs to determine by the type of machine the package
   3.258 +will run on.  Usually, assuming the package is built to be run on the
   3.259 +_same_ architectures, `configure' can figure that out, but if it prints
   3.260 +a message saying it cannot guess the machine type, give it the
   3.261 +`--build=TYPE' option.  TYPE can either be a short name for the system
   3.262 +type, such as `sun4', or a canonical name which has the form:
   3.263 +
   3.264 +     CPU-COMPANY-SYSTEM
   3.265 +
   3.266 +where SYSTEM can have one of these forms:
   3.267 +
   3.268 +     OS
   3.269 +     KERNEL-OS
   3.270 +
   3.271 +   See the file `config.sub' for the possible values of each field.  If
   3.272 +`config.sub' isn't included in this package, then this package doesn't
   3.273 +need to know the machine type.
   3.274 +
   3.275 +   If you are _building_ compiler tools for cross-compiling, you should
   3.276 +use the option `--target=TYPE' to select the type of system they will
   3.277 +produce code for.
   3.278 +
   3.279 +   If you want to _use_ a cross compiler, that generates code for a
   3.280 +platform different from the build platform, you should specify the
   3.281 +"host" platform (i.e., that on which the generated programs will
   3.282 +eventually be run) with `--host=TYPE'.
   3.283 +
   3.284 +Sharing Defaults
   3.285 +================
   3.286 +
   3.287 +   If you want to set default values for `configure' scripts to share,
   3.288 +you can create a site shell script called `config.site' that gives
   3.289 +default values for variables like `CC', `cache_file', and `prefix'.
   3.290 +`configure' looks for `PREFIX/share/config.site' if it exists, then
   3.291 +`PREFIX/etc/config.site' if it exists.  Or, you can set the
   3.292 +`CONFIG_SITE' environment variable to the location of the site script.
   3.293 +A warning: not all `configure' scripts look for a site script.
   3.294 +
   3.295 +Defining Variables
   3.296 +==================
   3.297 +
   3.298 +   Variables not defined in a site shell script can be set in the
   3.299 +environment passed to `configure'.  However, some packages may run
   3.300 +configure again during the build, and the customized values of these
   3.301 +variables may be lost.  In order to avoid this problem, you should set
   3.302 +them in the `configure' command line, using `VAR=value'.  For example:
   3.303 +
   3.304 +     ./configure CC=/usr/local2/bin/gcc
   3.305 +
   3.306 +causes the specified `gcc' to be used as the C compiler (unless it is
   3.307 +overridden in the site shell script).
   3.308 +
   3.309 +Unfortunately, this technique does not work for `CONFIG_SHELL' due to
   3.310 +an Autoconf bug.  Until the bug is fixed you can use this workaround:
   3.311 +
   3.312 +     CONFIG_SHELL=/bin/bash /bin/bash ./configure CONFIG_SHELL=/bin/bash
   3.313 +
   3.314 +`configure' Invocation
   3.315 +======================
   3.316 +
   3.317 +   `configure' recognizes the following options to control how it
   3.318 +operates.
   3.319 +
   3.320 +`--help'
   3.321 +`-h'
   3.322 +     Print a summary of all of the options to `configure', and exit.
   3.323 +
   3.324 +`--help=short'
   3.325 +`--help=recursive'
   3.326 +     Print a summary of the options unique to this package's
   3.327 +     `configure', and exit.  The `short' variant lists options used
   3.328 +     only in the top level, while the `recursive' variant lists options
   3.329 +     also present in any nested packages.
   3.330 +
   3.331 +`--version'
   3.332 +`-V'
   3.333 +     Print the version of Autoconf used to generate the `configure'
   3.334 +     script, and exit.
   3.335 +
   3.336 +`--cache-file=FILE'
   3.337 +     Enable the cache: use and save the results of the tests in FILE,
   3.338 +     traditionally `config.cache'.  FILE defaults to `/dev/null' to
   3.339 +     disable caching.
   3.340 +
   3.341 +`--config-cache'
   3.342 +`-C'
   3.343 +     Alias for `--cache-file=config.cache'.
   3.344 +
   3.345 +`--quiet'
   3.346 +`--silent'
   3.347 +`-q'
   3.348 +     Do not print messages saying which checks are being made.  To
   3.349 +     suppress all normal output, redirect it to `/dev/null' (any error
   3.350 +     messages will still be shown).
   3.351 +
   3.352 +`--srcdir=DIR'
   3.353 +     Look for the package's source code in directory DIR.  Usually
   3.354 +     `configure' can determine that directory automatically.
   3.355 +
   3.356 +`--prefix=DIR'
   3.357 +     Use DIR as the installation prefix.  *note Installation Names::
   3.358 +     for more details, including other options available for fine-tuning
   3.359 +     the installation locations.
   3.360 +
   3.361 +`--no-create'
   3.362 +`-n'
   3.363 +     Run the configure checks, but stop before creating any output
   3.364 +     files.
   3.365 +
   3.366 +`configure' also accepts some other, not widely useful, options.  Run
   3.367 +`configure --help' for more details.
   3.368 +

     4.1 --- a/configure.ac	Sat Mar 03 10:50:33 2012 -0600
     4.2 +++ b/configure.ac	Sat Mar 03 10:54:39 2012 -0600
     4.3 @@ -1,5 +1,9 @@
     4.4  AC_INIT([vba-rlm], [1.0])
     4.5  
     4.6 +AC_CONFIG_FILES([Makefile 
     4.7 +	         src/Makefile
     4.8 +                 src/lua/Makefile])
     4.9 +
    4.10  AM_INIT_AUTOMAKE([dist-bzip2])
    4.11  
    4.12  AC_OUTPUT