--- jocaml-3.11.2.a.orig/debian/copyright
+++ jocaml-3.11.2.a/debian/copyright
@@ -0,0 +1,652 @@
+This package was debianized by Mehdi Dogguy <dogguy@pps.jussieu.fr> on
+Sat, 16 Feb 2008 18:21:23 +0000.
+
+It was downloaded from <http://jocaml.inria.fr/pub/distri/jocaml-3.10/>
+
+Upstream authors :
+
+ Luc Maranget <Luc.Maranget@inria.fr>
+ Ma Qin <Qin.Ma@inria.fr>
+ Louis Mandel <Louis.Mandel@inria.fr>
+ Xavier Leroy <xavier.leroy@inria.fr>
+ Jerome Vouillon <vouillon@pps.jussieu.fr>
+ Damien Doligez <damien.doligez@inria.fr>
+
+Copyright:
+
+ Copyright 2000-2009 Institut National de Recherche en Informatique et en
+ Automatique (INRIA).
+
+License:
+
+ JoCaml licence is exactly Objective Caml's licence:
+
+In the following, "the Library" refers to all files marked "Copyright
+INRIA" in the following directories and their sub-directories:
+
+ asmrun, byterun, camlp4, config, otherlibs, stdlib, win32caml
+
+and "the Compiler" refers to all files marked "Copyright INRIA" in the
+following directories and their sub-directories:
+
+ asmcomp, boot, bytecomp, debugger, driver, lex, ocamldoc, parsing,
+ tools, toplevel, typing, utils, yacc
+
+The Compiler is distributed under the terms of the Q Public License
+version 1.0 with a change to choice of law (included below).
+
+The Library is distributed under the terms of the GNU Library General
+Public License version 2 (included below).
+
+As a special exception to the Q Public Licence, you may develop
+application programs, reusable components and other software items
+that link with the original or modified versions of the Compiler
+and are not made available to the general public, without any of the
+additional requirements listed in clause 6c of the Q Public licence.
+
+As a special exception to the GNU Library General Public License, you
+may link, statically or dynamically, a "work that uses the Library"
+with a publicly distributed version of the Library to produce an
+executable file containing portions of the Library, and distribute
+that executable file under terms of your choice, without any of the
+additional requirements listed in clause 6 of the GNU Library General
+Public License. By "a publicly distributed version of the Library",
+we mean either the unmodified Library as distributed by INRIA, or a
+modified version of the Library that is distributed under the
+conditions defined in clause 2 of the GNU Library General Public
+License. This exception does not however invalidate any other reasons
+why the executable file might be covered by the GNU Library General
+Public License.
+
+----------------------------------------------------------------------
+
+ THE Q PUBLIC LICENSE version 1.0
+
+ Copyright (C) 1999 Troll Tech AS, Norway.
+ Everyone is permitted to copy and
+ distribute this license document.
+
+The intent of this license is to establish freedom to share and change
+the software regulated by this license under the open source model.
+
+This license applies to any software containing a notice placed by the
+copyright holder saying that it may be distributed under the terms of
+the Q Public License version 1.0. Such software is herein referred to
+as the Software. This license covers modification and distribution of
+the Software, use of third-party application programs based on the
+Software, and development of free software which uses the Software.
+
+ Granted Rights
+
+1. You are granted the non-exclusive rights set forth in this license
+provided you agree to and comply with any and all conditions in this
+license. Whole or partial distribution of the Software, or software
+items that link with the Software, in any form signifies acceptance of
+this license.
+
+2. You may copy and distribute the Software in unmodified form
+provided that the entire package, including - but not restricted to -
+copyright, trademark notices and disclaimers, as released by the
+initial developer of the Software, is distributed.
+
+3. You may make modifications to the Software and distribute your
+modifications, in a form that is separate from the Software, such as
+patches. The following restrictions apply to modifications:
+
+ a. Modifications must not alter or remove any copyright notices
+ in the Software.
+
+ b. When modifications to the Software are released under this
+ license, a non-exclusive royalty-free right is granted to the
+ initial developer of the Software to distribute your
+ modification in future versions of the Software provided such
+ versions remain available under these terms in addition to any
+ other license(s) of the initial developer.
+
+4. You may distribute machine-executable forms of the Software or
+machine-executable forms of modified versions of the Software,
+provided that you meet these restrictions:
+
+ a. You must include this license document in the distribution.
+
+ b. You must ensure that all recipients of the machine-executable
+ forms are also able to receive the complete machine-readable
+ source code to the distributed Software, including all
+ modifications, without any charge beyond the costs of data
+ transfer, and place prominent notices in the distribution
+ explaining this.
+
+ c. You must ensure that all modifications included in the
+ machine-executable forms are available under the terms of this
+ license.
+
+5. You may use the original or modified versions of the Software to
+compile, link and run application programs legally developed by you or
+by others.
+
+6. You may develop application programs, reusable components and other
+software items that link with the original or modified versions of the
+Software. These items, when distributed, are subject to the following
+requirements:
+
+ a. You must ensure that all recipients of machine-executable
+ forms of these items are also able to receive and use the
+ complete machine-readable source code to the items without any
+ charge beyond the costs of data transfer.
+
+ b. You must explicitly license all recipients of your items to
+ use and re-distribute original and modified versions of the
+ items in both machine-executable and source code forms. The
+ recipients must be able to do so without any charges whatsoever,
+ and they must be able to re-distribute to anyone they choose.
+
+ c. If the items are not available to the general public, and the
+ initial developer of the Software requests a copy of the items,
+ then you must supply one.
+
+ Limitations of Liability
+
+In no event shall the initial developers or copyright holders be
+liable for any damages whatsoever, including - but not restricted to -
+lost revenue or profits or other direct, indirect, special, incidental
+or consequential damages, even if they have been advised of the
+possibility of such damages, except to the extent invariable law, if
+any, provides otherwise.
+
+ No Warranty
+
+The Software and this license document are provided AS IS with NO
+WARRANTY OF ANY KIND, INCLUDING THE WARRANTY OF DESIGN,
+MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
+
+ Choice of Law
+
+This license is governed by the Laws of France.
+
+----------------------------------------------------------------------
+
+ GNU LIBRARY GENERAL PUBLIC LICENSE
+ Version 2, June 1991
+
+ Copyright (C) 1991 Free Software Foundation, Inc.
+ 51 Franklin St, Fifth Floor, Boston, MA 02110-1301, USA.
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+[This is the first released version of the library GPL. It is
+ numbered 2 because it goes with version 2 of the ordinary GPL.]
+
+ Preamble
+
+ The licenses for most software are designed to take away your
+freedom to share and change it. By contrast, the GNU General Public
+Licenses are intended to guarantee your freedom to share and change
+free software--to make sure the software is free for all its users.
+
+ This license, the Library General Public License, applies to some
+specially designated Free Software Foundation software, and to any
+other libraries whose authors decide to use it. You can use it for
+your libraries, too.
+
+ When we speak of free software, we are referring to freedom, not
+price. Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+this service if you wish), that you receive source code or can get it
+if you want it, that you can change the software or use pieces of it
+in new free programs; and that you know you can do these things.
+
+ To protect your rights, we need to make restrictions that forbid
+anyone to deny you these rights or to ask you to surrender the rights.
+These restrictions translate to certain responsibilities for you if
+you distribute copies of the library, or if you modify it.
+
+ For example, if you distribute copies of the library, whether gratis
+or for a fee, you must give the recipients all the rights that we gave
+you. You must make sure that they, too, receive or can get the source
+code. If you link a program with the library, you must provide
+complete object files to the recipients so that they can relink them
+with the library, after making changes to the library and recompiling
+it. And you must show them these terms so they know their rights.
+
+ Our method of protecting your rights has two steps: (1) copyright
+the library, and (2) offer you this license which gives you legal
+permission to copy, distribute and/or modify the library.
+
+ Also, for each distributor's protection, we want to make certain
+that everyone understands that there is no warranty for this free
+library. If the library is modified by someone else and passed on, we
+want its recipients to know that what they have is not the original
+version, so that any problems introduced by others will not reflect on
+the original authors' reputations.
+
+ Finally, any free program is threatened constantly by software
+patents. We wish to avoid the danger that companies distributing free
+software will individually obtain patent licenses, thus in effect
+transforming the program into proprietary software. To prevent this,
+we have made it clear that any patent must be licensed for everyone's
+free use or not licensed at all.
+
+ Most GNU software, including some libraries, is covered by the ordinary
+GNU General Public License, which was designed for utility programs. This
+license, the GNU Library General Public License, applies to certain
+designated libraries. This license is quite different from the ordinary
+one; be sure to read it in full, and don't assume that anything in it is
+the same as in the ordinary license.
+
+ The reason we have a separate public license for some libraries is that
+they blur the distinction we usually make between modifying or adding to a
+program and simply using it. Linking a program with a library, without
+changing the library, is in some sense simply using the library, and is
+analogous to running a utility program or application program. However, in
+a textual and legal sense, the linked executable is a combined work, a
+derivative of the original library, and the ordinary General Public License
+treats it as such.
+
+ Because of this blurred distinction, using the ordinary General
+Public License for libraries did not effectively promote software
+sharing, because most developers did not use the libraries. We
+concluded that weaker conditions might promote sharing better.
+
+ However, unrestricted linking of non-free programs would deprive the
+users of those programs of all benefit from the free status of the
+libraries themselves. This Library General Public License is intended to
+permit developers of non-free programs to use free libraries, while
+preserving your freedom as a user of such programs to change the free
+libraries that are incorporated in them. (We have not seen how to achieve
+this as regards changes in header files, but we have achieved it as regards
+changes in the actual functions of the Library.) The hope is that this
+will lead to faster development of free libraries.
+
+ The precise terms and conditions for copying, distribution and
+modification follow. Pay close attention to the difference between a
+"work based on the library" and a "work that uses the library". The
+former contains code derived from the library, while the latter only
+works together with the library.
+
+ Note that it is possible for a library to be covered by the ordinary
+General Public License rather than by this special one.
+
+ GNU LIBRARY GENERAL PUBLIC LICENSE
+ TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+ 0. This License Agreement applies to any software library which
+contains a notice placed by the copyright holder or other authorized
+party saying it may be distributed under the terms of this Library
+General Public License (also called "this License"). Each licensee is
+addressed as "you".
+
+ A "library" means a collection of software functions and/or data
+prepared so as to be conveniently linked with application programs
+(which use some of those functions and data) to form executables.
+
+ The "Library", below, refers to any such software library or work
+which has been distributed under these terms. A "work based on the
+Library" means either the Library or any derivative work under
+copyright law: that is to say, a work containing the Library or a
+portion of it, either verbatim or with modifications and/or translated
+straightforwardly into another language. (Hereinafter, translation is
+included without limitation in the term "modification".)
+
+ "Source code" for a work means the preferred form of the work for
+making modifications to it. For a library, complete source code means
+all the source code for all modules it contains, plus any associated
+interface definition files, plus the scripts used to control compilation
+and installation of the library.
+
+ Activities other than copying, distribution and modification are not
+covered by this License; they are outside its scope. The act of
+running a program using the Library is not restricted, and output from
+such a program is covered only if its contents constitute a work based
+on the Library (independent of the use of the Library in a tool for
+writing it). Whether that is true depends on what the Library does
+and what the program that uses the Library does.
+
+ 1. You may copy and distribute verbatim copies of the Library's
+complete source code as you receive it, in any medium, provided that
+you conspicuously and appropriately publish on each copy an
+appropriate copyright notice and disclaimer of warranty; keep intact
+all the notices that refer to this License and to the absence of any
+warranty; and distribute a copy of this License along with the
+Library.
+
+ You may charge a fee for the physical act of transferring a copy,
+and you may at your option offer warranty protection in exchange for a
+fee.
+
+ 2. You may modify your copy or copies of the Library or any portion
+of it, thus forming a work based on the Library, and copy and
+distribute such modifications or work under the terms of Section 1
+above, provided that you also meet all of these conditions:
+
+ a) The modified work must itself be a software library.
+
+ b) You must cause the files modified to carry prominent notices
+ stating that you changed the files and the date of any change.
+
+ c) You must cause the whole of the work to be licensed at no
+ charge to all third parties under the terms of this License.
+
+ d) If a facility in the modified Library refers to a function or a
+ table of data to be supplied by an application program that uses
+ the facility, other than as an argument passed when the facility
+ is invoked, then you must make a good faith effort to ensure that,
+ in the event an application does not supply such function or
+ table, the facility still operates, and performs whatever part of
+ its purpose remains meaningful.
+
+ (For example, a function in a library to compute square roots has
+ a purpose that is entirely well-defined independent of the
+ application. Therefore, Subsection 2d requires that any
+ application-supplied function or table used by this function must
+ be optional: if the application does not supply it, the square
+ root function must still compute square roots.)
+
+These requirements apply to the modified work as a whole. If
+identifiable sections of that work are not derived from the Library,
+and can be reasonably considered independent and separate works in
+themselves, then this License, and its terms, do not apply to those
+sections when you distribute them as separate works. But when you
+distribute the same sections as part of a whole which is a work based
+on the Library, the distribution of the whole must be on the terms of
+this License, whose permissions for other licensees extend to the
+entire whole, and thus to each and every part regardless of who wrote
+it.
+
+Thus, it is not the intent of this section to claim rights or contest
+your rights to work written entirely by you; rather, the intent is to
+exercise the right to control the distribution of derivative or
+collective works based on the Library.
+
+In addition, mere aggregation of another work not based on the Library
+with the Library (or with a work based on the Library) on a volume of
+a storage or distribution medium does not bring the other work under
+the scope of this License.
+
+ 3. You may opt to apply the terms of the ordinary GNU General Public
+License instead of this License to a given copy of the Library. To do
+this, you must alter all the notices that refer to this License, so
+that they refer to the ordinary GNU General Public License, version 2,
+instead of to this License. (If a newer version than version 2 of the
+ordinary GNU General Public License has appeared, then you can specify
+that version instead if you wish.) Do not make any other change in
+these notices.
+
+ Once this change is made in a given copy, it is irreversible for
+that copy, so the ordinary GNU General Public License applies to all
+subsequent copies and derivative works made from that copy.
+
+ This option is useful when you wish to copy part of the code of
+the Library into a program that is not a library.
+
+ 4. You may copy and distribute the Library (or a portion or
+derivative of it, under Section 2) in object code or executable form
+under the terms of Sections 1 and 2 above provided that you accompany
+it with the complete corresponding machine-readable source code, which
+must be distributed under the terms of Sections 1 and 2 above on a
+medium customarily used for software interchange.
+
+ If distribution of object code is made by offering access to copy
+from a designated place, then offering equivalent access to copy the
+source code from the same place satisfies the requirement to
+distribute the source code, even though third parties are not
+compelled to copy the source along with the object code.
+
+ 5. A program that contains no derivative of any portion of the
+Library, but is designed to work with the Library by being compiled or
+linked with it, is called a "work that uses the Library". Such a
+work, in isolation, is not a derivative work of the Library, and
+therefore falls outside the scope of this License.
+
+ However, linking a "work that uses the Library" with the Library
+creates an executable that is a derivative of the Library (because it
+contains portions of the Library), rather than a "work that uses the
+library". The executable is therefore covered by this License.
+Section 6 states terms for distribution of such executables.
+
+ When a "work that uses the Library" uses material from a header file
+that is part of the Library, the object code for the work may be a
+derivative work of the Library even though the source code is not.
+Whether this is true is especially significant if the work can be
+linked without the Library, or if the work is itself a library. The
+threshold for this to be true is not precisely defined by law.
+
+ If such an object file uses only numerical parameters, data
+structure layouts and accessors, and small macros and small inline
+functions (ten lines or less in length), then the use of the object
+file is unrestricted, regardless of whether it is legally a derivative
+work. (Executables containing this object code plus portions of the
+Library will still fall under Section 6.)
+
+ Otherwise, if the work is a derivative of the Library, you may
+distribute the object code for the work under the terms of Section 6.
+Any executables containing that work also fall under Section 6,
+whether or not they are linked directly with the Library itself.
+
+ 6. As an exception to the Sections above, you may also compile or
+link a "work that uses the Library" with the Library to produce a
+work containing portions of the Library, and distribute that work
+under terms of your choice, provided that the terms permit
+modification of the work for the customer's own use and reverse
+engineering for debugging such modifications.
+
+ You must give prominent notice with each copy of the work that the
+Library is used in it and that the Library and its use are covered by
+this License. You must supply a copy of this License. If the work
+during execution displays copyright notices, you must include the
+copyright notice for the Library among them, as well as a reference
+directing the user to the copy of this License. Also, you must do one
+of these things:
+
+ a) Accompany the work with the complete corresponding
+ machine-readable source code for the Library including whatever
+ changes were used in the work (which must be distributed under
+ Sections 1 and 2 above); and, if the work is an executable linked
+ with the Library, with the complete machine-readable "work that
+ uses the Library", as object code and/or source code, so that the
+ user can modify the Library and then relink to produce a modified
+ executable containing the modified Library. (It is understood
+ that the user who changes the contents of definitions files in the
+ Library will not necessarily be able to recompile the application
+ to use the modified definitions.)
+
+ b) Accompany the work with a written offer, valid for at
+ least three years, to give the same user the materials
+ specified in Subsection 6a, above, for a charge no more
+ than the cost of performing this distribution.
+
+ c) If distribution of the work is made by offering access to copy
+ from a designated place, offer equivalent access to copy the above
+ specified materials from the same place.
+
+ d) Verify that the user has already received a copy of these
+ materials or that you have already sent this user a copy.
+
+ For an executable, the required form of the "work that uses the
+Library" must include any data and utility programs needed for
+reproducing the executable from it. However, as a special exception,
+the source code distributed need not include anything that is normally
+distributed (in either source or binary form) with the major
+components (compiler, kernel, and so on) of the operating system on
+which the executable runs, unless that component itself accompanies
+the executable.
+
+ It may happen that this requirement contradicts the license
+restrictions of other proprietary libraries that do not normally
+accompany the operating system. Such a contradiction means you cannot
+use both them and the Library together in an executable that you
+distribute.
+
+ 7. You may place library facilities that are a work based on the
+Library side-by-side in a single library together with other library
+facilities not covered by this License, and distribute such a combined
+library, provided that the separate distribution of the work based on
+the Library and of the other library facilities is otherwise
+permitted, and provided that you do these two things:
+
+ a) Accompany the combined library with a copy of the same work
+ based on the Library, uncombined with any other library
+ facilities. This must be distributed under the terms of the
+ Sections above.
+
+ b) Give prominent notice with the combined library of the fact
+ that part of it is a work based on the Library, and explaining
+ where to find the accompanying uncombined form of the same work.
+
+ 8. You may not copy, modify, sublicense, link with, or distribute
+the Library except as expressly provided under this License. Any
+attempt otherwise to copy, modify, sublicense, link with, or
+distribute the Library is void, and will automatically terminate your
+rights under this License. However, parties who have received copies,
+or rights, from you under this License will not have their licenses
+terminated so long as such parties remain in full compliance.
+
+ 9. You are not required to accept this License, since you have not
+signed it. However, nothing else grants you permission to modify or
+distribute the Library or its derivative works. These actions are
+prohibited by law if you do not accept this License. Therefore, by
+modifying or distributing the Library (or any work based on the
+Library), you indicate your acceptance of this License to do so, and
+all its terms and conditions for copying, distributing or modifying
+the Library or works based on it.
+
+ 10. Each time you redistribute the Library (or any work based on the
+Library), the recipient automatically receives a license from the
+original licensor to copy, distribute, link with or modify the Library
+subject to these terms and conditions. You may not impose any further
+restrictions on the recipients' exercise of the rights granted herein.
+You are not responsible for enforcing compliance by third parties to
+this License.
+
+ 11. If, as a consequence of a court judgment or allegation of patent
+infringement or for any other reason (not limited to patent issues),
+conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License. If you cannot
+distribute so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you
+may not distribute the Library at all. For example, if a patent
+license would not permit royalty-free redistribution of the Library by
+all those who receive copies directly or indirectly through you, then
+the only way you could satisfy both it and this License would be to
+refrain entirely from distribution of the Library.
+
+If any portion of this section is held invalid or unenforceable under any
+particular circumstance, the balance of the section is intended to apply,
+and the section as a whole is intended to apply in other circumstances.
+
+It is not the purpose of this section to induce you to infringe any
+patents or other property right claims or to contest validity of any
+such claims; this section has the sole purpose of protecting the
+integrity of the free software distribution system which is
+implemented by public license practices. Many people have made
+generous contributions to the wide range of software distributed
+through that system in reliance on consistent application of that
+system; it is up to the author/donor to decide if he or she is willing
+to distribute software through any other system and a licensee cannot
+impose that choice.
+
+This section is intended to make thoroughly clear what is believed to
+be a consequence of the rest of this License.
+
+ 12. If the distribution and/or use of the Library is restricted in
+certain countries either by patents or by copyrighted interfaces, the
+original copyright holder who places the Library under this License may add
+an explicit geographical distribution limitation excluding those countries,
+so that distribution is permitted only in or among countries not thus
+excluded. In such case, this License incorporates the limitation as if
+written in the body of this License.
+
+ 13. The Free Software Foundation may publish revised and/or new
+versions of the Library General Public License from time to time.
+Such new versions will be similar in spirit to the present version,
+but may differ in detail to address new problems or concerns.
+
+Each version is given a distinguishing version number. If the Library
+specifies a version number of this License which applies to it and
+"any later version", you have the option of following the terms and
+conditions either of that version or of any later version published by
+the Free Software Foundation. If the Library does not specify a
+license version number, you may choose any version ever published by
+the Free Software Foundation.
+
+ 14. If you wish to incorporate parts of the Library into other free
+programs whose distribution conditions are incompatible with these,
+write to the author to ask for permission. For software which is
+copyrighted by the Free Software Foundation, write to the Free
+Software Foundation; we sometimes make exceptions for this. Our
+decision will be guided by the two goals of preserving the free status
+of all derivatives of our free software and of promoting the sharing
+and reuse of software generally.
+
+ NO WARRANTY
+
+ 15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO
+WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
+EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
+OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY
+KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
+PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE
+LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME
+THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+ 16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN
+WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY
+AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU
+FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR
+CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
+LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING
+RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A
+FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF
+SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
+DAMAGES.
+
+ END OF TERMS AND CONDITIONS
+
+ Appendix: How to Apply These Terms to Your New Libraries
+
+ If you develop a new library, and you want it to be of the greatest
+possible use to the public, we recommend making it free software that
+everyone can redistribute and change. You can do so by permitting
+redistribution under these terms (or, alternatively, under the terms of the
+ordinary General Public License).
+
+ To apply these terms, attach the following notices to the library. It is
+safest to attach them to the start of each source file to most effectively
+convey the exclusion of warranty; and each file should have at least the
+"copyright" line and a pointer to where the full notice is found.
+
+ <one line to give the library's name and a brief idea of what it does.>
+ Copyright (C) <year> <name of author>
+
+ This library is free software; you can redistribute it and/or
+ modify it under the terms of the GNU Library General Public
+ License as published by the Free Software Foundation; either
+ version 2 of the License, or (at your option) any later version.
+
+ This library 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
+ Library General Public License for more details.
+
+ You should have received a copy of the GNU Library General Public
+ License along with this library; if not, write to the Free Software
+ Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301,
+ USA.
+
+Also add information on how to contact you by electronic and paper mail.
+
+You should also get your employer (if you work as a programmer) or your
+school, if any, to sign a "copyright disclaimer" for the library, if
+necessary. Here is a sample; alter the names:
+
+ Yoyodyne, Inc., hereby disclaims all copyright interest in the
+ library `Frob' (a library for tweaking knobs) written by James Random Hacker.
+
+ <signature of Ty Coon>, 1 April 1990
+ Ty Coon, President of Vice
+
+That's all there is to it!
+
+The Debian packaging is (C) 2008, Mehdi Dogguy <dogguy@pps.jussieu.fr> and
+is licensed under the GPL, see `/usr/share/common-licenses/GPL'.
--- jocaml-3.11.2.a.orig/debian/jocaml-base.manpages
+++ jocaml-3.11.2.a/debian/jocaml-base.manpages
@@ -0,0 +1 @@
+debian/man/jocamlrun.1
--- jocaml-3.11.2.a.orig/debian/changelog
+++ jocaml-3.11.2.a/debian/changelog
@@ -0,0 +1,77 @@
+jocaml (3.11.2.a-1) unstable; urgency=low
+
+ * s/A/a/ in version number (Closes: #569893)
+ * Use automatic dependencies computed by dh-ocaml (>= 0.9)
+
+ -- Mehdi Dogguy <mehdi@debian.org> Wed, 17 Feb 2010 12:35:10 +0100
+
+jocaml (3.11.2.A-1) unstable; urgency=low
+
+ * New Upstream version
+
+ -- Mehdi Dogguy <mehdi@debian.org> Fri, 12 Feb 2010 15:54:59 +0100
+
+jocaml (3.11.1-3) unstable; urgency=low
+
+ * Copy config.{sub,guess} to ./config/gnu/, fixes FTBFS on avr32
+ (Closes: #548117, #538049).
+ * Use dh_ocamlinit to handle *.in files (Closes: #549779).
+
+ -- Mehdi Dogguy <mehdi@debian.org> Sat, 31 Oct 2009 16:55:02 +0100
+
+jocaml (3.11.1-2) unstable; urgency=low
+
+ * Fix bashim in debian/jocamlmktop and add a copyright notice
+ (Closes: #547748).
+ * Update my email address and remove DMUA
+ * Bump standards to 3.8.3, no changes needed
+ * Update short description for jocaml-base
+
+ -- Mehdi Dogguy <mehdi@debian.org> Tue, 22 Sep 2009 20:07:22 +0200
+
+jocaml (3.11.1-1) unstable; urgency=low
+
+ * New Upstream Version
+ * Install toplevel library, Closes: #532989, #532981.
+ * Make ocaml-findlib work with JoCaml, Closes: #532970, by:
+ - Adding a patch to minimize changes in outcometree.mli
+ - Installing toploop.cmi in a new directory (/usr/lib/jocaml/jocamltoploop)
+ - Modifying jocamlmktop so that produced toplevel is expunged from some
+ modules: Parsetree, types and Env.
+ - Adding a patch for expunge which adds a -v option to give modules to
+ filter instead of modules to keep.
+ * Tools addlabels and scrapelabels are not installed by upstream anymore
+ * Use ocamlinit sed rule to generate links for opt programs
+ * Bump standards to 3.8.2
+ * Add a README.source
+ * New JoCaml standard library location is: /usr/lib/jocaml/
+
+ -- Mehdi Dogguy <dogguy@pps.jussieu.fr> Tue, 23 Jun 2009 17:51:44 +0200
+
+jocaml (3.11.0-3) unstable; urgency=low
+
+ [ Stefano Zacchiroli ]
+ * set archive section to "ocaml"
+
+ [ Mehdi Dogguy ]
+ * Fix FTBFS on non-native archs: do not install asmrun*
+
+ -- Mehdi Dogguy <dogguy@pps.jussieu.fr> Tue, 07 Apr 2009 14:03:33 +0200
+
+jocaml (3.11.0-2) unstable; urgency=low
+
+ * Do not install opt binaries and native files on non-native architecures,
+ closes: #522504.
+ * Add DMUA flag, with Sam's blessing.
+
+ -- Mehdi Dogguy <dogguy@pps.jussieu.fr> Sat, 04 Apr 2009 13:23:34 +0200
+
+jocaml (3.11.0-1) unstable; urgency=low
+
+ [ Mehdi Dogguy ]
+ * Initial release, closes: #451797.
+
+ [ Samuel Mimram ]
+ * Updated packaging.
+
+ -- Samuel Mimram <smimram@debian.org> Wed, 11 Feb 2009 17:07:24 +0100
--- jocaml-3.11.2.a.orig/debian/rules
+++ jocaml-3.11.2.a/debian/rules
@@ -0,0 +1,72 @@
+#!/usr/bin/make -f
+# -*- makefile -*-
+
+export DH_VERBOSE=1
+
+include /usr/share/ocaml/ocamlvars.mk
+
+export DH_OPTIONS
+
+JOCAML_ABI := $(shell head -1 VERSION)
+JOCAML_OPT_ARCH := $(OCAML_OPT_ARCH)
+JOCAML_STDLIB_DIR := /usr/lib/jocaml/
+OCAMLINIT_OPTS := "-e 's/@JOCamlABI@/$(JOCAML_ABI)/g' -e 's%@JOCamlStdlibDir@%$(JOCAML_STDLIB_DIR)%g'"
+
+OCAMLC := $(if $(wildcard /usr/bin/ocamlc.opt),/usr/bin/ocamlc.opt,/usr/bin/ocamlc)
+
+override_dh_auto_configure:
+ OCAMLINIT_SED=$(OCAMLINIT_OPTS) dh_ocamlinit
+ for ext in sub guess; do \
+ if [ -f /usr/share/misc/config.$$ext ]; then \
+ cp -f /usr/share/misc/config.$$ext $(CURDIR)/config/gnu/config.$$ext; \
+ fi; \
+ done
+ ./configure --prefix /usr \
+ --libdir $(JOCAML_STDLIB_DIR) \
+ --mandir /usr/share/man \
+ --host $(DEB_HOST_GNU_TYPE) \
+ -ocamlc $(OCAMLC) \
+ -no-curses
+
+override_dh_auto_build:
+ if test ! -d boot.debian; then \
+ cp -xa boot boot.debian; \
+ fi
+ $(MAKE) world
+ifdef JOCAML_OPT_ARCH
+ $(MAKE) opt opt.opt
+endif
+
+override_dh_auto_clean:
+ dh_ocamlinit -d
+ $(RM) -f $(OFILES)
+ if [ -f Makefile -a -f config/Makefile ]; then \
+ $(MAKE) clean; \
+ fi
+ if test -d boot.debian; then \
+ $(RM) -r boot; \
+ mv boot.debian boot; \
+ fi
+
+override_dh_auto_install:
+ mkdir -p $(CURDIR)/debian/tmp/usr
+ $(MAKE) PREFIX=$(CURDIR)/debian/tmp/usr LIBDIR=$(CURDIR)/debian/tmp/$(JOCAML_STDLIB_DIR) install
+ mv $(CURDIR)/debian/tmp/$(JOCAML_STDLIB_DIR)/toploop.cmi $(CURDIR)/debian/jocaml/$(JOCAML_STDLIB_DIR)/jocamltoploop/
+ cd $(CURDIR)/debian/tmp/usr/bin; \
+ for i in ocamldep ocamldep.opt ocamlprof ocamlcp ocamlmklib; do \
+ if [ -e $$i ]; then mv $$i j$$i; fi; \
+ done
+ cp -f debian/jocamlmktop $(CURDIR)/debian/tmp/usr/bin
+ $(RM) -f $(CURDIR)/debian/tmp/usr/bin/ocamlmktop
+ mkdir -p debian/tmp/usr/share/lintian/overrides
+ cp debian/jocaml.lintian-overrides debian/tmp/usr/share/lintian/overrides/jocaml
+ echo 'F:JOCamlABI=$(JOCAML_ABI)' >> debian/jocaml.substvars
+ echo 'F:OCamlABI=$(OCAML_ABI)' >> debian/jocaml.substvars
+ echo 'F:JOCamlABI=$(JOCAML_ABI)' >> debian/jocaml-base.substvars
+
+override_dh_ocaml:
+ dh_ocaml --checksum=$(JOCAML_ABI) --runtime-map=jocaml:jocaml-base -Xtoplevellib.cma \
+ --nodefined-map=jocaml:Topdirs,Toploop,Topmain,Topstart,Condition,Thread,ThreadUnix,Event,Mutex,UnixLabels,Unix
+
+%:
+ dh --with quilt,ocaml $@
--- jocaml-3.11.2.a.orig/debian/control
+++ jocaml-3.11.2.a/debian/control
@@ -0,0 +1,52 @@
+Source: jocaml
+Section: ocaml
+Priority: optional
+Maintainer: Debian OCaml Maintainers <debian-ocaml-maint@lists.debian.org>
+Uploaders:
+ Mehdi Dogguy <mehdi@debian.org>,
+ Samuel Mimram <smimram@debian.org>
+Build-Depends:
+ debhelper (>= 7.0.52),
+ quilt (>= 0.46-7),
+ autotools-dev,
+ libx11-dev,
+ libncurses5-dev,
+ libgdbm-dev,
+ dh-ocaml (>= 0.9),
+ ocaml-nox (>= 3.11)
+Homepage: http://jocaml.inria.fr/
+Standards-Version: 3.8.3
+Vcs-Git: git://git.debian.org/git/pkg-ocaml-maint/packages/jocaml.git
+Vcs-Browser: http://git.debian.org/?p=pkg-ocaml-maint/packages/jocaml.git
+
+Package: jocaml
+Architecture: any
+Depends:
+ ${shlibs:Depends},
+ ${misc:Depends},
+ ${ocaml:Depends}
+Provides:
+ ${ocaml:Provides}
+Description: OCaml extended for concurrent and distributed programming
+ The JOCaml programming language is an extension of the OCaml language with
+ high-level prmitives for communication and synchronization between processes.
+ This enables programmers to rapidly develop distributed large-scale
+ applications using the expressivity of OCaml.
+
+Package: jocaml-base
+Architecture: any
+Depends:
+ ${shlibs:Depends},
+ ${misc:Depends},
+ ${ocaml:Depends}
+Provides:
+ ${ocaml:Provides}
+Description: Runtime system for JOCaml bytecode executables
+ The JOCaml programming language is an extension of the OCaml language with
+ high-level prmitives for communication and synchronization between processes.
+ This enables programmers to rapidly develop distributed large-scale
+ applications using the expressivity of OCaml.
+ .
+ This package contains only the runtime system needed to run bytecode
+ executables. The 'jocaml' package contains the full development suite of
+ JOCaml.
--- jocaml-3.11.2.a.orig/debian/clean
+++ jocaml-3.11.2.a/debian/clean
@@ -0,0 +1,7 @@
+myocamlbuild_config.ml
+debian/jocaml.links
+config/config.sh
+config/Makefile
+config/m.h
+config/s.h
+tools/myocamlbuild_config.ml
--- jocaml-3.11.2.a.orig/debian/jocaml.dirs.in
+++ jocaml-3.11.2.a/debian/jocaml.dirs.in
@@ -0,0 +1,4 @@
+usr/bin
+@JOCamlStdlibDir@
+@JOCamlStdlibDir@/jocamltoploop
+usr/share/lintian/overrides
--- jocaml-3.11.2.a.orig/debian/jocaml-base.install.in
+++ jocaml-3.11.2.a/debian/jocaml-base.install.in
@@ -0,0 +1,8 @@
+usr/bin/jocamlrun
+@JOCamlStdlibDir@/ld.conf
+@JOCamlStdlibDir@/stublibs/*thread*
+@JOCamlStdlibDir@/threads/join.cma
+@JOCamlStdlibDir@/threads/threads.cma
+@JOCamlStdlibDir@/vmthreads/join.cma
+@JOCamlStdlibDir@/vmthreads/threads.cma
+@JOCamlStdlibDir@/vmthreads/unix.cma
--- jocaml-3.11.2.a.orig/debian/compat
+++ jocaml-3.11.2.a/debian/compat
@@ -0,0 +1 @@
+7
--- jocaml-3.11.2.a.orig/debian/jocamlmktop
+++ jocaml-3.11.2.a/debian/jocamlmktop
@@ -0,0 +1,25 @@
+#!/bin/sh
+
+# Copyright (C) 2009 Mehdi Dogguy <dogguy@pps.jussieu.fr>
+# You have permission to copy, modify, and redistribute under the
+# terms of the GPL-3.0. For full license terms, see gpl-3.0.txt.
+
+set -e
+
+jocamlc -I /usr/lib/jocaml/jocamltoploop/ -linkall toplevellib.cma "$@" topstart.cmo
+
+if [ $? -eq 0 ] ; then
+ TOP=`echo $@ | sed -n 's/.*-o \([^ ]*\).*/\1/gp'`
+ if [ "$TOP" = "" ] ; then
+ TOP="a.out"
+ fi
+ if [ ! -f "$TOP" ] ; then
+ echo "$0: The generated toplevel doesn't exist"
+ exit 1
+ else
+ TMP=`mktemp`
+ mv $TOP $TMP
+ /usr/lib/jocaml/expunge $TMP $TOP -v Parsetree Env Types
+ rm -f $TMP
+ fi
+fi
--- jocaml-3.11.2.a.orig/debian/jocaml.lintian-overrides.in
+++ jocaml-3.11.2.a/debian/jocaml.lintian-overrides.in
@@ -0,0 +1,12 @@
+jocaml: script-not-executable .@JOCamlStdlibDir@camlheader
+jocaml: unusual-interpreter ./usr/bin/jocaml #!/usr/bin/jocamlrun
+jocaml: unusual-interpreter ./usr/bin/jocamlc #!/usr/bin/jocamlrun
+jocaml: unusual-interpreter ./usr/bin/jocamlcp #!/usr/bin/jocamlrun
+jocaml: unusual-interpreter ./usr/bin/jocamldep #!/usr/bin/jocamlrun
+jocaml: unusual-interpreter ./usr/bin/jocamllex #!/usr/bin/jocamlrun
+jocaml: unusual-interpreter ./usr/bin/jocamlmklib #!/usr/bin/jocamlrun
+jocaml: unusual-interpreter ./usr/bin/jocamlopt #!/usr/bin/jocamlrun
+jocaml: unusual-interpreter ./usr/bin/jocamlprof #!/usr/bin/jocamlrun
+jocaml: unusual-interpreter .@JOCamlStdlibDir@camlheader #!/usr/bin/jocamlrun
+jocaml: unusual-interpreter .@JOCamlStdlibDir@expunge #!/usr/bin/jocamlrun
+jocaml: unusual-interpreter .@JOCamlStdlibDir@extract_crc #!/usr/bin/jocamlrun
--- jocaml-3.11.2.a.orig/debian/jocaml.install.in
+++ jocaml-3.11.2.a/debian/jocaml.install.in
@@ -0,0 +1,34 @@
+usr/bin/jocaml
+usr/bin/jocamlc
+usr/bin/jocamlcp
+usr/bin/jocamldep
+usr/bin/jocamllex
+usr/bin/jocamlmklib
+usr/bin/jocamlmktop
+usr/bin/jocamlprof
+usr/bin/jocamlyacc
+OPT: usr/bin/jocamlc.opt
+OPT: usr/bin/jocamldep.opt
+OPT: usr/bin/jocamllex.opt
+OPT: usr/bin/jocamlopt
+OPT: usr/bin/jocamlopt.opt
+@JOCamlStdlibDir@/topdirs.cmi
+@JOCamlStdlibDir@/toplevellib.cma
+@JOCamlStdlibDir@/topmain.cmi
+@JOCamlStdlibDir@/topstart.cmo
+@JOCamlStdlibDir@/camlheader*
+@JOCamlStdlibDir@/expunge
+@JOCamlStdlibDir@/extract_crc
+@JOCamlStdlibDir@/Makefile.config
+@JOCamlStdlibDir@/libcamlrun*
+@JOCamlStdlibDir@/threads/*.mli
+@JOCamlStdlibDir@/threads/*.cmi
+@JOCamlStdlibDir@/vmthreads/*.mli
+@JOCamlStdlibDir@/vmthreads/*.cmi
+OPT: @JOCamlStdlibDir@/*thread*.a
+OPT: @JOCamlStdlibDir@/threads/*.a
+OPT: @JOCamlStdlibDir@/threads/*.cmxa
+OPT: @JOCamlStdlibDir@/threads/*.cmx
+OPT: @JOCamlStdlibDir@/vmthreads/*.a
+OPT: @JOCamlStdlibDir@/libasmrun*
+usr/share/lintian/overrides/jocaml
--- jocaml-3.11.2.a.orig/debian/watch
+++ jocaml-3.11.2.a/debian/watch
@@ -0,0 +1,3 @@
+version=3
+opts=dversionmangle=s/\+debian.?// \
+http://jocaml.inria.fr/pub/distri/jocaml-(.*)/jocaml-(.*)\.tar\.gz
--- jocaml-3.11.2.a.orig/debian/jocaml.manpages
+++ jocaml-3.11.2.a/debian/jocaml.manpages
@@ -0,0 +1,10 @@
+debian/man/jocaml.1
+debian/man/jocamlc.1
+debian/man/jocamlcp.1
+debian/man/jocamldep.1
+debian/man/jocamllex.1
+debian/man/jocamlmktop.1
+debian/man/jocamlopt.1
+debian/man/jocamlprof.1
+debian/man/jocamlyacc.1
+debian/man/jocamlmklib.1
--- jocaml-3.11.2.a.orig/debian/gbp.conf
+++ jocaml-3.11.2.a/debian/gbp.conf
@@ -0,0 +1,2 @@
+[DEFAULT]
+pristine-tar = True
--- jocaml-3.11.2.a.orig/debian/jocaml.links.in
+++ jocaml-3.11.2.a/debian/jocaml.links.in
@@ -0,0 +1,4 @@
+OPT: usr/share/man/man1/jocamlc.1.gz usr/share/man/man1/jocamlc.opt.1.gz
+OPT: usr/share/man/man1/jocamlopt.1.gz usr/share/man/man1/jocamlopt.opt.1.gz
+OPT: usr/share/man/man1/jocamllex.1.gz usr/share/man/man1/jocamllex.opt.1.gz
+OPT: usr/share/man/man1/jocamldep.1.gz usr/share/man/man1/jocamldep.opt.1.gz
--- jocaml-3.11.2.a.orig/debian/README.source
+++ jocaml-3.11.2.a/debian/README.source
@@ -0,0 +1,16 @@
+jocaml Debian source package
+============================
+
+Patching upstream sources
+-------------------------
+
+This source package uses quilt to apply and remove its patches. Please
+refer to `/usr/share/doc/quilt/README.source' for information about
+how to use quilt for source packages.
+
+The quilt series is generated from the Git repository, using
+dom-{apply,save}-patches, from the dh-ocaml (>= 0.4.2) package. Please
+refer to the appendix about Git in the Debian OCaml Packaging Policy
+(from the same package).
+
+ -- Mehdi Dogguy <dogguy@pps.jussieu.fr>, Tue, 07 Jul 2009 23:15:06 +0200
--- jocaml-3.11.2.a.orig/debian/man/jocamlcp.1
+++ jocaml-3.11.2.a/debian/man/jocamlcp.1
@@ -0,0 +1,99 @@
+\" $Id: ocamlcp.m,v 1.4 2008/09/15 14:05:30 doligez Exp $
+
+.TH JOCAMLCP 1
+
+.SH NAME
+Jocamlcp \- The JoCaml profiling compiler
+
+.SH SYNOPSIS
+.B jocamlcp
+[
+.I jocamlcp options
+]
+[
+.BI \-p \ flags
+]
+.I filename ...
+
+.SH DESCRIPTION
+The
+.B jocamlcp
+command is a front-end to
+.BR jocamlc (1)
+that instruments the source code, adding code to record how many times
+functions are called, branches of conditionals are taken, ...
+Execution of instrumented code produces an execution profile in the
+file ocamlprof.dump, which can be read using
+.BR jocamlprof (1).
+
+.B jocamlcp
+accepts the same arguments and options as
+.BR jocamlc (1).
+
+.SH OPTIONS
+
+In addition to the
+.BR jocamlc (1)
+options,
+.B jocamlcp
+accepts the following option controlling the amount of profiling
+information:
+.TP
+.BI \-p \ letters
+The
+.I letters
+indicate which parts of the program should be profiled:
+.TP
+.B a
+all options
+.TP
+.B f
+function calls : a count point is set at the beginning of each function body
+.TP
+.B i
+.BR if \ ... \ then \ ... \ else :
+count points are set in both
+.BR then \ and \ else
+branches
+.TP
+.B l
+\BR while , \ for
+loops: a count point is set at the beginning of the loop body
+.TP
+.B m
+.B match
+branches: a count point is set at the beginning of the
+body of each branch of a pattern-matching
+.TP
+.B t
+.BR try \ ... \ with
+branches: a count point is set at the beginning of the body of each
+branch of an exception catcher
+
+.PP
+For instance, compiling with
+.B jocamlcp\ \-pfilm
+profiles function calls,
+.BR if \ ... \ then \ ... \ else \ ...,
+loops, and pattern matching.
+
+Calling
+.BR jocamlcp (1)
+without the
+.B \-p
+option defaults to
+.B \-p\ fm
+meaning that only function calls and pattern matching are profiled.
+
+Note: due to the implementation of streams and stream patterns as
+syntactic sugar, it is hard to predict what parts of stream expressions
+and patterns will be profiled by a given flag. To profile a program with
+streams, we recommend using
+.BR jocamlcp\ \-p\ a .
+
+.SH SEE ALSO
+.BR jocamlc (1),
+.BR jocamlprof (1).
+.br
+.IR "The Objective Caml user's manual" ,
+chapter "Profiling".
--- jocaml-3.11.2.a.orig/debian/man/jocamlmklib.1
+++ jocaml-3.11.2.a/debian/man/jocamlmklib.1
@@ -0,0 +1,127 @@
+.\" Hey, EMACS: -*- nroff -*-
+.TH JOCAMLMKLIB 1 "August 19, 2004"
+.SH NAME
+jocamlmklib \- generate libraries with mixed C / Caml code.
+.SH SYNOPSIS
+.B ocalmklib
+.RI [ options ] " files"
+.SH DESCRIPTION
+The
+.B jocamlmklib
+command facilitates the construction of libraries containing both Caml code and C code, and usable both in static linking and dynamic linking modes.
+.SH OPTIONS
+.TP
+.B \-h, \-\-help
+Show summary of options.
+.TP
+.BI \-cclib\ lib
+C library passed to jocamlc
+.B \-a
+or
+.BR jocamlopt (1)
+.B \-a
+only.
+.TP
+.BI \-ccopt\ opt
+C option passed to
+.BR jocamlc (1)
+.B \-a
+or
+.BR jocamlopt (1)
+.B \-a
+only.
+.TP
+.B \-custom
+Disable dynamic loading.
+.TP
+.BI \-dllpath\ dir
+Add
+.I dir
+to the run-time search path for DLLs.
+.TP
+.BI \-I\ dir
+Add
+.I dir
+to the path searched for Caml object files.
+.TP
+.B \-failsafe
+Fall back to static linking if DLL construction failed.
+.TP
+.BI \-ldopt\ opt
+C option passed to the shared linker only.
+.TP
+.B \-linkall
+Build Caml archive with link-all behavior.
+.TP
+.BI \-l lib
+Specify a dependent C library.
+.TP
+.BI \-L dir
+Add
+.I dir
+to the path searched for C libraries.
+.TP
+.BI \-jocamlc\ cmd
+Use
+.I cmd
+in place of
+.BR jocamlc (1).
+.TP
+.BI \-jocamlopt\ cmd
+Use
+.I cmd
+in place of
+.BR jocamlopt (1).
+.TP
+.BI \-o\ name
+Generated Caml library is named
+.IR name .cma
+or
+.IR name .cmxa.
+.TP
+.BI \-oc\ name
+Generated C library is named
+.RI dll name .so
+or
+.RI lib name .a.
+.TP
+.BI \-rpath\ dir
+Same as
+.B \-dllpath
+.IR dir .
+.TP
+.BI \-R dir
+Same as
+.BR \-rpath .
+.TP
+.B \-verbose
+Print commands before executing them.
+.TP
+\fB\-Wl\fR, \fB\-rpath \fIdir
+Same as
+.B \-dllpath
+.IR dir .
+.TP
+\fB\-Wl\fR, \fB\-rpath\ \-Wl \fIdir
+Same as
+.B \-dllpath
+.IR dir .
+.TP
+\fB\-Wl\fR, \fB\-R\fIdir
+Same as
+.B \-dllpath
+.IR dir .
+.TP
+.BI \-F dir
+Specify a framework directory (MacOSX).
+.TP
+.BI \-framework\ name
+Use framework
+.I name
+(MacOSX).
+.SH SEE ALSO
+.BR jocamlc (1),
+.BR jocamlopt (1).
+.SH AUTHOR
+This manual page was written by Samuel Mimram <samuel.mimram@ens-lyon.org>,
+for the Debian project (but may be used by others).
--- jocaml-3.11.2.a.orig/debian/man/jocamldep.1
+++ jocaml-3.11.2.a/debian/man/jocamldep.1
@@ -0,0 +1,79 @@
+.TH JOCAMLDEP 1
+
+.SH NAME
+jocamldep \- Dependency generator for JoCaml
+
+.SH SYNOPSIS
+.B jocamldep
+[
+.BI \-I \ lib-dir
+]
+.I filename ...
+
+.SH DESCRIPTION
+
+The
+.BR jocamldep (1)
+command scans a set of Objective Caml source files
+(.ml and .mli files) for references to external compilation units,
+and outputs dependency lines in a format suitable for the
+.BR make (1)
+utility. This ensures that make will compile the source files in the
+correct order, and recompile those files that need to when a source
+file is modified.
+
+The typical usage is:
+.P
+jocamldep
+.I options
+*.mli *.ml > .depend
+.P
+where .depend is the file that should contain the
+dependencies.
+
+Dependencies are generated both for compiling with the bytecode
+compiler
+.BR jocamlc (1)
+and with the native-code compiler
+.BR jocamlopt (1).
+
+.SH OPTIONS
+
+The following command-line option is recognized by
+.BR jocamldep (1).
+
+.TP
+.BI \-I \ directory
+Add the given directory to the list of directories searched for
+source files. If a source file foo.ml mentions an external
+compilation unit Bar, a dependency on that unit's interface
+bar.cmi is generated only if the source for bar is found in the
+current directory or in one of the directories specified with
+.BR -I .
+Otherwise, Bar is assumed to be a module form the standard library,
+and no dependencies are generated. For programs that span multiple
+directories, it is recommended to pass
+.BR jocamldep (1)
+the same -I options that are passed to the compiler.
+
+.TP
+.BI \-native
+Generate dependencies for a pure native-code program (no bytecode
+version). When an implementation file (.ml file) has no explicit
+interface file (.mli file),
+.BR jocamldep (1)
+generates dependencies on the
+bytecode compiled file (.cmo file) to reflect interface changes.
+This can cause unnecessary bytecode recompilations for programs that
+are compiled to native-code only. The flag
+.BR -native
+causes dependencies on native compiled files (.cmx) to be generated instead
+of on .cmo files. (This flag makes no difference if all source files
+have explicit .mli interface files.)
+
+.SH SEE ALSO
+.BR jocamlc (1),
+.BR jocamlopt (1).
+.br
+.I The Objective Caml user's manual,
+chapter "Dependency generator".
--- jocaml-3.11.2.a.orig/debian/man/jocamllex.1
+++ jocaml-3.11.2.a/debian/man/jocamllex.1
@@ -0,0 +1,71 @@
+.TH JOCAMLLEX 1
+
+.SH NAME
+jocamllex \- The JoCaml lexer generator
+
+.SH SYNOPSIS
+.B jocamllex
+[
+.BI \-o \ output-file
+]
+[
+.B \-ml
+]
+.I filename.mll
+
+.SH DESCRIPTION
+
+The
+.BR jocamllex (1)
+command generates Objective Caml lexers from a set of regular
+expressions with associated semantic actions, in the style of
+.BR lex (1).
+
+Running
+.BR jocamllex (1)
+on the input file
+.IR lexer \&.mll
+produces Caml code for a lexical analyzer in file
+.IR lexer \&.ml.
+
+This file defines one lexing function per entry point in the lexer
+definition. These functions have the same names as the entry
+points. Lexing functions take as argument a lexer buffer, and return
+the semantic attribute of the corresponding entry point.
+
+Lexer buffers are an abstract data type implemented in the standard
+library module Lexing. The functions Lexing.from_channel,
+Lexing.from_string and Lexing.from_function create
+lexer buffers that read from an input channel, a character string, or
+any reading function, respectively.
+
+When used in conjunction with a parser generated by
+.BR jocamlyacc (1),
+the semantic actions compute a value belonging to the type token defined
+by the generated parsing module.
+
+.SH OPTIONS
+
+The
+.BR jocamllex (1)
+command recognizes the following options:
+
+.TP
+.BI \-o \ output-file
+Specify the output file name
+.IR output-file
+instead of the default naming convention.
+
+.TP
+.B \-ml
+Output code that does not use the Caml built-in automata
+interpreter. Instead, the automaton is encoded by Caml functions.
+This option is useful for debugging
+.BR jocamllex (1),
+using it for production lexers is not recommended.
+
+.SH SEE ALSO
+.BR jocamlyacc (1).
+.br
+.I The Objective Caml user's manual,
+chapter "Lexer and parser generators".
--- jocaml-3.11.2.a.orig/debian/man/jocamlopt.1
+++ jocaml-3.11.2.a/debian/man/jocamlopt.1
@@ -0,0 +1,231 @@
+.TH JOCAMLOPT 1
+
+.SH NAME
+jocamlopt \- The JoCaml native-code compiler
+
+
+.SH SYNOPSIS
+.B jocamlopt
+[
+.B \-acivS
+]
+[
+.BI \-cclib \ libname
+]
+[
+.BI \-ccopt \ option
+]
+[
+.B \-compact
+]
+[
+.B \-unsafe
+]
+[
+.BI \-o \ exec-file
+]
+[
+.BI \-I \ lib-dir
+]
+.I filename ...
+
+.B jocamlopt.opt
+.I (same options)
+
+.SH DESCRIPTION
+The JoCaml high-performance
+native-code compiler
+.BR jocamlopt (1)
+compiles Caml source files to native code object files and link these
+object files to produce standalone executables.
+
+The
+.BR jocamlopt (1)
+command has a command-line interface very close to that
+of
+.BR jocamlc (1).
+It accepts the same types of arguments and processes them
+sequentially:
+
+Arguments ending in .mli are taken to be source files for
+compilation unit interfaces. Interfaces specify the names exported by
+compilation units: they declare value names with their types, define
+public data types, declare abstract data types, and so on. From the
+file
+.IR x \&.mli,
+the
+.BR jocamlopt (1)
+compiler produces a compiled interface
+in the file
+.IR x \&.cmi.
+The interface produced is identical to that
+produced by the bytecode compiler
+.BR jocamlc (1).
+
+Arguments ending in .ml are taken to be source files for compilation
+unit implementations. Implementations provide definitions for the
+names exported by the unit, and also contain expressions to be
+evaluated for their side-effects. From the file
+.IR x \&.ml,
+the
+.BR jocamlopt (1)
+compiler produces two files:
+.IR x \&.o,
+containing native object code, and
+.IR x \&.cmx,
+containing extra information for linking and
+optimization of the clients of the unit. The compiled implementation
+should always be referred to under the name
+.IR x \&.cmx
+(when given a .o file,
+.BR jocamlopt (1)
+assumes that it contains code compiled from C, not from Caml).
+
+The implementation is checked against the interface file
+.IR x \&.mli
+(if it exists) as described in the manual for
+.BR jocamlc (1).
+
+Arguments ending in .cmx are taken to be compiled object code. These
+files are linked together, along with the object files obtained
+by compiling .ml arguments (if any), and the Caml Light standard
+library, to produce a native-code executable program. The order in
+which .cmx and .ml arguments are presented on the command line is
+relevant: compilation units are initialized in that order at
+run-time, and it is a link-time error to use a component of a unit
+before having initialized it. Hence, a given
+.IR x \&.cmx
+file must come
+before all .cmx files that refer to the unit
+.IR x .
+
+Arguments ending in .cmxa are taken to be libraries of object code.
+Such a library packs in two files
+.IR lib \&.cmxa
+and
+.IR lib \&.a
+a set of object files (.cmx/.o files). Libraries are build with
+.B jocamlopt \-a
+(see the description of the
+.B \-a
+option below). The object
+files contained in the library are linked as regular .cmx files (see
+above), in the order specified when the library was built. The only
+difference is that if an object file contained in a library is not
+referenced anywhere in the program, then it is not linked in.
+
+Arguments ending in .c are passed to the C compiler, which generates
+a .o object file. This object file is linked with the program.
+
+Arguments ending in .o or .a are assumed to be C object files and
+libraries. They are linked with the program.
+
+The output of the linking phase is a regular Unix executable file. It
+does not need
+.BR jocamlrun (1)
+to run.
+
+.B jocamlopt.opt
+is the same compiler as
+.BR jocamlopt ,
+but compiled with itself instead of with the bytecode compiler
+.BR jocamlc (1).
+Thus, it behaves exactly like
+.BR jocamlopt ,
+but compiles faster.
+.B jocamlopt.opt
+is not available in all installations of JoCaml.
+
+.SH OPTIONS
+
+The following command-line options are recognized by
+.BR jocamlopt (1).
+
+.TP
+.B \-a
+Build a library (.cmxa/.a file) with the object files (.cmx/.o
+files) given on the command line, instead of linking them into an
+executable file. The name of the library can be set with the
+.B \-o
+option. The default name is library.cmxa.
+
+.TP
+.B \-c
+Compile only. Suppress the linking phase of the
+compilation. Source code files are turned into compiled files, but no
+executable file is produced. This option is useful to
+compile modules separately.
+
+.TP
+.BI \-cclib\ -l libname
+Pass the
+.BI -l libname
+option to the linker. This causes the given C library to be linked
+with the program.
+
+.TP
+.BI \-ccopt \ option
+Pass the given option to the C compiler and linker. For instance,
+.B -ccopt -L
+.I dir
+causes the C linker to search for C libraries in
+directory
+.IR dir .
+
+.TP
+.B \-compact
+Optimize the produced code for space rather than for time. This
+results in smaller but slightly slower programs. The default is to
+optimize for speed.
+
+.TP
+.B \-i
+Cause the compiler to print all defined names (with their inferred
+types or their definitions) when compiling an implementation (.ml
+file). This can be useful to check the types inferred by the
+compiler. Also, since the output follows the syntax of interfaces, it
+can help in writing an explicit interface (.mli file) for a file:
+just redirect the standard output of the compiler to a .mli file,
+and edit that file to remove all declarations of unexported names.
+
+.TP
+.BI \-I \ directory
+Add the given directory to the list of directories searched for
+compiled interface files (.cmi) and compiled object code files
+(.cmo). By default, the current directory is searched first, then the
+standard library directory. Directories added with -I are searched
+after the current directory, in the order in which they were given on
+the command line, but before the standard library directory.
+
+.TP
+.BI \-o \ exec-file
+Specify the name of the output file produced by the linker. The
+default output name is a.out, in keeping with the Unix tradition. If
+the
+.B \-a
+option is given, specify the name of the library produced.
+
+.TP
+.B \-S
+Keep the assembly code produced during the compilation. The assembly
+code for the source file
+.IR x \&.ml
+is saved in the file
+.IR x \&.s.
+
+.TP
+.B \-v
+Print the version number of the compiler.
+
+.TP
+.B \-unsafe
+Turn bound checking off on array and string accesses (the v.(i) and
+s.[i] constructs). Programs compiled with -unsafe are therefore
+faster, but unsafe: anything can happen if the program accesses an
+array or string outside of its bounds.
+
+.SH SEE ALSO
+.BR jocamlc (1).
+.br
+.I The Objective Caml user's manual,
+chapter "Native-code compilation".
--- jocaml-3.11.2.a.orig/debian/man/jocamlprof.1
+++ jocaml-3.11.2.a/debian/man/jocamlprof.1
@@ -0,0 +1,73 @@
+\" $Id: ocamlprof.m,v 1.6 2008/09/15 14:25:42 doligez Exp $
+.TH JOCAMLPROF 1
+
+.SH NAME
+jocamlprof \- The JoCaml profiler
+
+.SH SYNOPSIS
+.B jocamlprof
+[
+.BI \-f \ dump-file
+]
+[
+.BI \-F \ text
+]
+.I filename ...
+
+.SH DESCRIPTION
+The
+.B jocamlprof
+command prints execution counts gathered during the execution of a
+Objective Caml program instrumented with
+.BR jocamlcp (1).
+
+It produces a source listing of the program modules given as arguments
+where execution counts have been inserted as comments. For instance,
+
+.B jocamlprof foo.ml
+
+prints the source code for the foo module, with comments indicating
+how many times the functions in this module have been called. Naturally,
+this information is accurate only if the source file has not been modified
+since the profiling execution took place.
+
+.SH OPTIONS
+
+.TP
+.BI \-f \ dumpfile
+Specifies an alternate dump file of profiling information.
+.TP
+.BI \-F \ string
+Specifies an additional string to be output with profiling information.
+By default,
+.BR jocamlprof (1)
+will annotate programs with comments of the form
+.BI (* \ n \ *)
+where
+.I n
+is the counter value for a profiling point. With option
+.BI \-F \ s
+the annotation will be
+.BI (* \ sn \ *)
+.TP
+.BI \-impl \ filename
+Compile the file
+.I filename
+as an implementation file, even if its extension is not .ml.
+.TP
+.BI \-intf \ filename
+Compile the file
+.I filename
+as an interface file, even if its extension is not .mli.
+.TP
+.B \-version
+Print the version number of jocamlprof and exit.
+.TP
+.BR \-help \ or \ \-\-help
+Display a short usage summary and exit.
+
+.SH SEE ALSO
+.BR jocamlcp (1).
+.br
+.IR "The Objective Caml user's manual" ,
+chapter "Profiling".
--- jocaml-3.11.2.a.orig/debian/man/jocamlc.1
+++ jocaml-3.11.2.a/debian/man/jocamlc.1
@@ -0,0 +1,248 @@
+.TH JOCAMLC 1
+
+.SH NAME
+jocamlc \- The JoCaml bytecode compiler
+
+
+.SH SYNOPSIS
+.B jocamlc
+[
+.B \-aciv
+]
+[
+.BI \-cclib \ libname
+]
+[
+.BI \-ccopt \ option
+]
+[
+.B \-custom
+]
+[
+.B \-unsafe
+]
+[
+.BI \-o \ exec-file
+]
+[
+.BI \-I \ lib-dir
+]
+.I filename ...
+
+.B jocamlc.opt
+.I (same options)
+
+.SH DESCRIPTION
+
+The JoCaml bytecode compiler
+.BR jocamlc (1)
+compiles Caml source files to bytecode object files and link
+these object files to produce standalone bytecode executable files.
+These executable files are then run by the bytecode interpreter
+.BR jocamlrun (1).
+
+The
+.BR jocamlc (1)
+command has a command-line interface similar to the one of
+most C compilers. It accepts several types of arguments and processes them
+sequentially:
+
+Arguments ending in .mli are taken to be source files for
+compilation unit interfaces. Interfaces specify the names exported by
+compilation units: they declare value names with their types, define
+public data types, declare abstract data types, and so on. From the
+file
+.IR x \&.mli,
+the
+.BR jocamlc (1)
+compiler produces a compiled interface
+in the file
+.IR x \&.cmi.
+
+Arguments ending in .ml are taken to be source files for compilation
+unit implementations. Implementations provide definitions for the
+names exported by the unit, and also contain expressions to be
+evaluated for their side-effects. From the file
+.IR x \&.ml,
+the
+.BR jocamlc (1)
+compiler produces compiled object bytecode in the file
+.IR x \&.cmo.
+
+If the interface file
+.IR x \&.mli
+exists, the implementation
+.IR x \&.ml
+is checked against the corresponding compiled interface
+.IR x \&.cmi,
+which is assumed to exist. If no interface
+.IR x \&.mli
+is provided, the compilation of
+.IR x \&.ml
+produces a compiled interface file
+.IR x \&.cmi
+in addition to the compiled object code file
+.IR x \&.cmo.
+The file
+.IR x \&.cmi
+produced
+corresponds to an interface that exports everything that is defined in
+the implementation
+.IR x \&.ml.
+
+Arguments ending in .cmo are taken to be compiled object bytecode. These
+files are linked together, along with the object files obtained
+by compiling .ml arguments (if any), and the Caml Light standard
+library, to produce a standalone executable program. The order in
+which .cmo and.ml arguments are presented on the command line is
+relevant: compilation units are initialized in that order at
+run-time, and it is a link-time error to use a component of a unit
+before having initialized it. Hence, a given
+.IR x \&.cmo
+file must come before all .cmo files that refer to the unit
+.IR x .
+
+Arguments ending in .cma are taken to be libraries of object bytecode.
+A library of object bytecode packs in a single file a set of object
+bytecode files (.cmo files). Libraries are built with
+.B ocamlc \-a
+(see the description of the
+.B \-a
+option below). The object files
+contained in the library are linked as regular .cmo files (see above), in the order specified when the .cma file was built. The only difference is that if an object file
+contained in a library is not referenced anywhere in the program, then
+it is not linked in.
+
+Arguments ending in .c are passed to the C compiler, which generates a .o object file. This object file is linked with the program if the
+.B \-custom
+flag is set (see the description of
+.B \-custom
+below).
+
+Arguments ending in .o or .a are assumed to be C object files and
+libraries. They are passed to the C linker when linking in
+.B \-custom
+mode (see the description of
+.B \-custom
+below).
+
+.B jocamlc.opt
+is the same compiler as
+.BR jocamlc ,
+but compiled with the native-code compiler
+.BR jocamlopt (1).
+Thus, it behaves exactly like
+.BR jocamlc ,
+but compiles faster.
+.B jocamlc.opt
+is not available in all installations of JoCaml.
+
+.SH OPTIONS
+
+The following command-line options are recognized by
+.BR jocamlc (1).
+
+.TP
+.B \-a
+Build a library (.cma file) with the object files (.cmo files) given on the command line, instead of linking them into an executable
+file. The name of the library can be set with the
+.B \-o
+option. The default name is
+.BR library.cma .
+
+.TP
+.B \-c
+Compile only. Suppress the linking phase of the
+compilation. Source code files are turned into compiled files, but no
+executable file is produced. This option is useful to
+compile modules separately.
+
+.TP
+.BI \-cclib\ -l libname
+Pass the
+.BI \-l libname
+option to the C linker when linking in
+``custom runtime'' mode (see the
+.B \-custom
+option). This causes the
+given C library to be linked with the program.
+
+.TP
+.B \-ccopt
+Pass the given option to the C compiler and linker, when linking in
+``custom runtime'' mode (see the
+.B \-custom
+option). For instance,
+.B -ccopt -L
+.I dir
+causes the C linker to search for C libraries in
+directory
+.IR dir .
+
+.TP
+.B \-custom
+Link in ``custom runtime'' mode. In the default linking mode, the
+linker produces bytecode that is intended to be executed with the
+shared runtime system,
+.BR jocamlrun (1).
+In the custom runtime mode, the
+linker produces an output file that contains both the runtime system
+and the bytecode for the program. The resulting file is larger, but it
+can be executed directly, even if the
+.BR jocamlrun (1)
+command is not
+installed. Moreover, the ``custom runtime'' mode enables linking Caml
+code with user-defined C functions.
+
+.TP
+.B \-i
+Cause the compiler to print all defined names (with their inferred
+types or their definitions) when compiling an implementation (.ml
+file). This can be useful to check the types inferred by the
+compiler. Also, since the output follows the syntax of interfaces, it
+can help in writing an explicit interface (.mli file) for a file: just
+redirect the standard output of the compiler to a .mli file, and edit
+that file to remove all declarations of unexported names.
+
+.TP
+.BI \-I \ directory
+Add the given directory to the list of directories searched for
+compiled interface files (.cmi) and compiled object code files
+(.cmo). By default, the current directory is searched first, then the
+standard library directory. Directories added with
+.B -I
+are searched
+after the current directory, in the order in which they were given on
+the command line, but before the standard library directory.
+
+.TP
+.BI \-o \ exec-file
+Specify the name of the output file produced by the linker. The
+default output name is
+.BR a.out ,
+in keeping with the Unix tradition. If the
+.B \-a
+option is given, specify the name of the library produced.
+
+.TP
+.B \-v
+Print the version number of the compiler.
+
+.TP
+.B \-unsafe
+Turn bound checking off on array and string accesses (the
+.B v.(i)
+and
+.B s.[i]
+constructs). Programs compiled with
+.B \-unsafe
+are therefore
+slightly faster, but unsafe: anything can happen if the program
+accesses an array or string outside of its bounds.
+
+.SH SEE ALSO
+.BR jocaml (1),
+.BR jocamlrun (1).
+.br
+.I The Objective Caml user's manual,
+chapter "Batch compilation".
--- jocaml-3.11.2.a.orig/debian/man/jocaml.1
+++ jocaml-3.11.2.a/debian/man/jocaml.1
@@ -0,0 +1,101 @@
+.TH JOCAML 1
+
+.SH NAME
+jocaml \- The JoCaml interactive toplevel
+
+
+.SH SYNOPSIS
+.B jocaml
+[
+.B \-unsafe
+]
+[
+.BI \-I \ lib-dir
+]
+[
+.I object-files
+]
+[
+.I script-file
+]
+.SH DESCRIPTION
+
+The
+.BR jocaml (1)
+command is the toplevel system for JoCaml,
+that permits interactive use of the JoCaml system through a
+read-eval-print loop. In this mode, the system repeatedly reads Caml
+phrases from the input, then typechecks, compiles and evaluates
+them, then prints the inferred type and result value, if any. The
+system prints a # (sharp) prompt before reading each phrase.
+
+A toplevel phrase can span several lines. It is terminated by ;; (a
+double-semicolon). The syntax of toplevel phrases is as follows.
+
+The toplevel system is started by the command
+.BR jocaml (1).
+Phrases are read on standard input, results are printed on standard
+output, errors on standard error. End-of-file on standard input
+terminates
+.BR jocaml (1).
+
+If one or more
+.I object-files
+(ending in
+.B .cmo
+or
+.B .cma
+ ) are given, they are loaded silently before starting the toplevel.
+
+If a
+.I script-file
+is given, phrases are read silently from the file, errors printed on
+standard error.
+.BR jocaml (1)
+exits after the execution of the last phrase.
+
+.SH OPTIONS
+
+The following command-line options are recognized by
+.BR jocaml (1).
+
+.TP
+.BI \-I \ directory
+Add the given directory to the list of directories searched for
+source and compiled files. By default, the current directory is
+searched first, then the standard library directory. Directories added
+with
+.B \-I
+are searched after the current directory, in the order in which they
+were given on the command line, but before the standard library
+directory.
+
+.TP
+.B \-unsafe
+Turn bound checking off on array and string accesses (the v.(i)
+and s.[i] constructs). Programs compiled with
+.B \-unsafe
+are therefore slightly faster, but unsafe: anything can happen if the program
+accesses an array or string outside of its bounds.
+
+.SH ENVIRONMENT VARIABLES
+
+.TP
+.B LC_CTYPE
+If set to iso_8859_1, accented characters (from the
+ISO Latin-1 character set) in string and character literals are
+printed as is; otherwise, they are printed as decimal escape sequences.
+
+.TP
+.B TERM
+When printing error messages, the toplevel system
+attempts to underline visually the location of the error. It
+consults the TERM variable to determines the type of output terminal
+and look up its capabilities in the terminal database.
+
+.SH SEE ALSO
+.BR jocamlc (1).
+.br
+.I The Objective Caml user's manual,
+chapter "The toplevel system".
+
--- jocaml-3.11.2.a.orig/debian/man/jocamlyacc.1
+++ jocaml-3.11.2.a/debian/man/jocamlyacc.1
@@ -0,0 +1,71 @@
+.TH JOCAMLYACC 1
+
+.SH NAME
+jocamlyacc \- The JoCaml parser generator
+
+.SH SYNOPSIS
+.B jocamlyacc
+[
+.B -v
+]
+[
+.BI \-b prefix
+]
+.I filename.mly
+
+.SH DESCRIPTION
+
+The
+.BR jocamlyacc (1)
+command produces a parser from a LALR(1) context-free grammar
+specification with attached semantic actions, in the style of
+.BR yacc (1).
+Assuming the input file is
+.IR grammar \&.mly,
+running
+.B jocamlyacc
+produces Caml code for a parser in the file
+.IR grammar \&.ml,
+and its interface in file
+.IR grammar \&.mli.
+
+The generated module defines one parsing function per entry point in
+the grammar. These functions have the same names as the entry points.
+Parsing functions take as arguments a lexical analyzer (a function
+from lexer buffers to tokens) and a lexer buffer, and return the
+semantic attribute of the corresponding entry point. Lexical analyzer
+functions are usually generated from a lexer specification by the
+.BR jocamllex (1)
+program. Lexer buffers are an abstract data type
+implemented in the standard library module Lexing. Tokens are values from
+the concrete type token, defined in the interface file
+.IR grammar \&.mli
+produced by
+.BR jocamlyacc (1).
+
+.SH OPTIONS
+
+The
+.BR jocamlyacc (1)
+command recognizes the following options:
+
+.TP
+.B \-v
+Generate a description of the parsing tables and a report on conflicts
+resulting from ambiguities in the grammar. The description is put in
+file
+.IR grammar \&.output.
+
+.TP
+.BI \-b prefix
+Name the output files
+.IR prefix \&.ml,
+.IR prefix \&.mli,
+.IR prefix \&.output,
+instead of the default naming convention.
+
+.SH SEE ALSO
+.BR jocamllex (1).
+.br
+.I The Objective Caml user's manual,
+chapter "Lexer and parser generators".
--- jocaml-3.11.2.a.orig/debian/man/jocamlrun.1
+++ jocaml-3.11.2.a/debian/man/jocamlrun.1
@@ -0,0 +1,139 @@
+.TH JOCAMLRUN 1
+
+.SH NAME
+jocamlrun \- The JoCaml bytecode interpreter
+
+.SH SYNOPSIS
+.B jocamlrun
+[
+.B \-v
+]
+.I filename argument ...
+
+.SH DESCRIPTION
+The
+.BR jocamlrun (1)
+command executes bytecode files produced by the
+linking phase of the
+.BR jocamlc (1)
+command.
+
+The first non-option argument is taken to be the name of the file
+containing the executable bytecode. (That file is searched in the
+executable path as well as in the current directory.) The remaining
+arguments are passed to the Objective Caml program, in the string array
+Sys.argv. Element 0 of this array is the name of the
+bytecode executable file; elements 1 to
+.I n
+are the remaining arguments.
+
+In most cases, the bytecode
+executable files produced by the
+.BR jocamlc (1)
+command are self-executable,
+and manage to launch the
+.BR jocamlrun (1)
+command on themselves automatically.
+
+.SH OPTIONS
+
+The following command-line option is recognized by
+.BR jocamlrun (1).
+
+.TP
+.B \-v
+When set, the memory manager prints verbose messages on standard error
+to signal garbage collections and heap extensions.
+
+.SH ENVIRONMENT VARIABLES
+
+The following environment variable are also consulted:
+
+.TP
+.B OCAMLRUNPARAM
+Set the garbage collection parameters.
+(If
+.B OCAMLRUNPARAM
+is not set,
+.B CAMLRUNPARAM
+will be used instead.)
+This variable must be a sequence of parameter specifications.
+A parameter specification is an option letter followed by an =
+sign, a decimal number, and an optional multiplier. There are seven
+options:
+.TP
+.BR b \ (backtrace)
+Print a stack backtrace in case of an uncaught exception.
+.TP
+.BR s \ (minor_heap_size)
+Size of the minor heap.
+.TP
+.BR i \ (major_heap_increment)
+Minimum size increment for the major heap.
+.TP
+.BR o \ (space_overhead)
+The major GC speed setting.
+.TP
+.BR O \ (max_overhead)
+The heap compaction trigger setting.
+.TP
+.BR l \ (stack_limit)
+The limit (in words) of the stack size.
+.TP
+.BR h
+The initial size of the major heap (in words).
+.TP
+.BR v \ (verbose)
+What GC messages to print to stderr. This is a sum of values selected
+from the following:
+.TP
+.BR 1
+Start of major GC cycle.
+.TP
+.BR 2
+Minor collection and major GC slice.
+.TP
+.BR 4
+Growing and shrinking of the heap.
+.TP
+.BR 8
+Resizing of stacks and memory manager tables.
+.TP
+.BR 16
+Heap compaction.
+.TP
+.BR 32
+Change of GC parameters.
+.TP
+.BR 64
+Computation of major GC slice size.
+.TP
+.BR 128
+Calling of finalisation function.
+.TP
+.BR 256
+Startup messages.
+
+The multiplier is
+.B k
+,
+.B M
+, or
+.B G
+, for multiplication by 2^10, 2^20, and 2^30 respectively.
+For example, on a 32-bit machine under bash, the command
+.B export OCAMLRUNPARAM='s=256k,v=1'
+tells a subsequent
+.B jocamlrun
+to set its initial minor heap size to 1 megabyte and to print
+a message at the start of each major GC cycle.
+
+.TP
+.B PATH
+List of directories searched to find the bytecode executable file.
+
+.SH SEE ALSO
+.BR jocamlc (1).
+.br
+.I The Objective Caml user's manual,
+chapter "Runtime system".
--- jocaml-3.11.2.a.orig/debian/man/jocamlmktop.1
+++ jocaml-3.11.2.a/debian/man/jocamlmktop.1
@@ -0,0 +1,84 @@
+.TH JOCAMLMKTOP 1
+
+.SH NAME
+jocamlmktop \- Building custom toplevel systems
+
+.SH SYNOPSIS
+.B jocamlmktop
+[
+.B \-v
+]
+[
+.BI \-cclib \ libname
+]
+[
+.BI \-ccopt \ option
+]
+[
+.B \-custom
+[
+.BI \-o \ exec-file
+]
+[
+.BI \-I \ lib-dir
+]
+.I filename ...
+
+.SH DESCRIPTION
+
+The
+.BR jocamlmktop (1)
+command builds JoCaml toplevels that
+contain user code preloaded at start-up.
+The
+.BR jocamlmktop (1)
+command takes as argument a set of
+.IR x \&.cmo
+and
+.IR x \&.cma
+files, and links them with the object files that implement the JoCaml toplevel. If the
+.B -custom
+flag is given, C object files and libraries (.o and .a files) can also
+be given on the command line and are linked in the resulting toplevel.
+
+.SH OPTIONS
+
+The following command-line options are recognized by
+.BR jocamlmktop (1).
+
+.TP
+.B \-v
+Print the version number of the compiler.
+
+.TP
+.BI \-cclib\ -l libname
+Pass the
+.BI \-l libname
+option to the C linker when linking in
+``custom runtime'' mode (see the corresponding option for
+.BR jocamlc (1).
+
+.TP
+.B \-ccopt
+Pass the given option to the C compiler and linker, when linking in
+``custom runtime'' mode. See the corresponding option for
+.BR jocamlc (1).
+
+.TP
+.B \-custom
+Link in ``custom runtime'' mode. See the corresponding option for
+.BR jocamlc (1).
+
+.TP
+.BI \-I directory
+Add the given directory to the list of directories searched for
+compiled interface files (.cmo and .cma).
+
+.TP
+.BI \-o \ exec-file
+Specify the name of the toplevel file produced by the linker.
+The default is is
+.BR a.out .
+
+.SH SEE ALSO
+.BR jocamlc (1).
--- jocaml-3.11.2.a.orig/debian/patches/0001-Replace-Otyp_proc-with-Otyp_stuff-to-make-outcometre.patch
+++ jocaml-3.11.2.a/debian/patches/0001-Replace-Otyp_proc-with-Otyp_stuff-to-make-outcometre.patch
@@ -0,0 +1,48 @@
+From: Mehdi Dogguy <dogguy@pps.jussieu.fr>
+Date: Tue, 23 Jun 2009 18:05:26 +0200
+Subject: [PATCH] Replace Otyp_proc with Otyp_stuff "" to make outcometree.mli compatible with the one from OCaml
+
+---
+ typing/oprint.ml | 1 -
+ typing/outcometree.mli | 1 -
+ typing/printtyp.ml | 2 +-
+ 3 files changed, 1 insertions(+), 3 deletions(-)
+
+diff --git a/typing/oprint.ml b/typing/oprint.ml
+index 825d550..3e254f7 100644
+--- a/typing/oprint.ml
++++ b/typing/oprint.ml
+@@ -209,7 +209,6 @@ and print_simple_out_type ppf =
+ | Otyp_alias _ | Otyp_poly _ | Otyp_arrow _ | Otyp_tuple _ as ty ->
+ fprintf ppf "@[<1>(%a)@]" print_out_type ty
+ | Otyp_abstract | Otyp_sum _ | Otyp_record _ | Otyp_manifest (_, _) -> ()
+- | Otyp_proc -> ()
+
+ and print_fields rest ppf =
+ function
+diff --git a/typing/outcometree.mli b/typing/outcometree.mli
+index aa3b327..8240e4b 100644
+--- a/typing/outcometree.mli
++++ b/typing/outcometree.mli
+@@ -60,7 +60,6 @@ type out_type =
+ | Otyp_variant of
+ bool * out_variant * bool * (string list) option
+ | Otyp_poly of string list * out_type
+- | Otyp_proc
+
+ and out_variant =
+ | Ovar_fields of (string * bool * out_type list) list
+diff --git a/typing/printtyp.ml b/typing/printtyp.ml
+index 978a773..a203e80 100644
+--- a/typing/printtyp.ml
++++ b/typing/printtyp.ml
+@@ -385,7 +385,7 @@ let rec tree_of_typexp sch ty =
+ end
+ | Tunivar ->
+ Otyp_var (false, name_of_type ty)
+- | Tproc _ -> Otyp_proc
++ | Tproc _ -> Otyp_stuff ""
+ in
+ if List.memq px !delayed then delayed := List.filter ((!=) px) !delayed;
+ if is_aliased px && aliasable ty then begin
+--
--- jocaml-3.11.2.a.orig/debian/patches/series
+++ jocaml-3.11.2.a/debian/patches/series
@@ -0,0 +1,2 @@
+0001-Replace-Otyp_proc-with-Otyp_stuff-to-make-outcometre.patch
+0002-Add-option-v-to-expunge-to-select-modules-to-filter-.patch
--- jocaml-3.11.2.a.orig/debian/patches/0002-Add-option-v-to-expunge-to-select-modules-to-filter-.patch
+++ jocaml-3.11.2.a/debian/patches/0002-Add-option-v-to-expunge-to-select-modules-to-filter-.patch
@@ -0,0 +1,51 @@
+From: Mehdi Dogguy <dogguy@pps.jussieu.fr>
+Date: Tue, 7 Jul 2009 18:03:42 +0200
+Subject: [PATCH] Add option -v to expunge to select modules to filter instead of modules to keep
+
+---
+ toplevel/expunge.ml | 22 ++++++++++++++--------
+ 1 files changed, 14 insertions(+), 8 deletions(-)
+
+diff --git a/toplevel/expunge.ml b/toplevel/expunge.ml
+index 05a4fe0..49fa91f 100644
+--- a/toplevel/expunge.ml
++++ b/toplevel/expunge.ml
+@@ -24,23 +24,29 @@ module StringSet =
+ let compare = compare
+ end)
+
++let is_exn =
++ let h = Hashtbl.create 64 in
++ Array.iter (fun n -> Hashtbl.add h n ()) Runtimedef.builtin_exceptions;
++ Hashtbl.mem h
++
+ let to_keep = ref StringSet.empty
+
++let negate = Sys.argv.(3) = "-v"
++
++let keep =
++ if negate then fun name -> is_exn name || not (StringSet.mem name !to_keep)
++ else fun name -> is_exn name || (StringSet.mem name !to_keep)
++
+ let expunge_map tbl =
+- Symtable.filter_global_map
+- (fun id -> StringSet.mem (Ident.name id) !to_keep)
+- tbl
++ Symtable.filter_global_map (fun id -> keep (Ident.name id)) tbl
+
+ let expunge_crcs tbl =
+- List.filter (fun (unit, crc) -> StringSet.mem unit !to_keep) tbl
++ List.filter (fun (unit, crc) -> keep unit) tbl
+
+ let main () =
+ let input_name = Sys.argv.(1) in
+ let output_name = Sys.argv.(2) in
+- Array.iter
+- (fun exn -> to_keep := StringSet.add exn !to_keep)
+- Runtimedef.builtin_exceptions;
+- for i = 3 to Array.length Sys.argv - 1 do
++ for i = (if negate then 4 else 3) to Array.length Sys.argv - 1 do
+ to_keep := StringSet.add (String.capitalize Sys.argv.(i)) !to_keep
+ done;
+ let ic = open_in_bin input_name in
+--
![[patchlogo]](http://patch-tracker.debian.org/static/img/swirlpatch.png)