Import v2.1.7-32bit.

INSTALL

@@ -9,11 +9,20 @@ Requirements:
     installation failures with 3.2.x)
   GNU make
 
+Optional dependencies:
+
+  xsltproc (from the GNOME XML library)
+
+    (If xsltproc is present, then installation will also create a set
+    of HTML files at <prefix>/lib/oo2c/oocdoc/html/.  The files
+    contain descriptions of the public interfaces of the library
+    modules.  Without xsltproc, or if it is manually disabled (see
+    PROBLEMS), then this step is skipped.)
+
 Additional requirements for "make test":
 
   GNU tar
   perl
-  xsltproc (from the GNOME XML library)
 
 
 Optional Packages

README

@@ -64,17 +64,13 @@ Building programs is simple as well:
 And then `bin/T' should say `Hello'.  For more information, please
 refer to the man page of oo2c.
 
-I'm mostly interested to hear about installation problems, compiler
-bugs (hangs, crashes, wrong error messages or warnings, or missing
-error messages), and usability issues.  Please use Sourceforge
+Please use Sourceforge
 
   https://sourceforge.net/tracker/?atid=103539&group_id=3539
 
 to report bugs and include the version you are using in the summary
 line.  This ensures that bug reports are not lost, and provides a
-convenient central location to collect information about bugs.  Bug
-reports accompanied by patches fixing the problem at hand are very
-welcome.
+convenient central location to collect information about bugs.
 
 For miscompiled code, that is, correct input code that produces a
 broken binary, please try to create a small program that will
@@ -85,13 +81,15 @@ trigger the bug, and the version of oo2c you are using.
 
 For input modules that hang or crash the compiler, please send me the
 module or modules that trigger the problem.  This does not need to be
-small.  Don't send me module fragments!
+small.  Don't send me module fragments!  Getting fragments into shape
+for the compiler to compile takes time that I would rather spend on
+debugging.
 
 Reporting about bugs can be a surprisingly difficult excercise in
 communication.  There is a very nice essay "How to Report Bugs
 Effectively" at http://www.chiark.greenend.org.uk/~sgtatham/bugs.html
-It should recommended reading for everyone who will ever write -- or
-read -- a bug report.
+It should be recommended reading for everyone who will ever write --
+or read -- a bug report.
 
 
 Build and Install Using a CVS Working Copy
@@ -110,7 +108,7 @@ Here are the recommended steps in detail.  First, the usual setup:
 
 Then create a compiler binary bin/oo2c from the current sources
 (~/local-ooc2/bin/oo2c is the local installation of the latest file
-release):
+release in this example):
 
   ~/sf-ooc/ooc2$ . ENV
   ~/sf-ooc/ooc2$ make $OOC_DEV_ROOT/oo2crc-install.xml
@@ -121,7 +119,7 @@ Use bin/oo2c to do "make install":
   ~/sf-ooc/ooc2$ make install BOOTSTRAP_COMPILER=bin/oo2c
 
 This installs the compiler's data under the configured prefix,
-`/tmp/test' in this example,
+`/tmp/test' from the call to ./configure above.
 
 
 How to Create a Patch

configure

@@ -1,6 +1,6 @@
 #! /bin/sh
 # Guess values for system-dependent variables and create Makefiles.
-# Generated by GNU Autoconf 2.59 for OOC 2.1.6.
+# Generated by GNU Autoconf 2.59 for OOC 2.1.7.
 #
 # Report bugs to <[email protected]>.
 #
@@ -269,8 +269,8 @@ SHELL=${CONFIG_SHELL-/bin/sh}
 # Identity of this package.
 PACKAGE_NAME='OOC'
 PACKAGE_TARNAME='ooc'
-PACKAGE_VERSION='2.1.6'
-PACKAGE_STRING='OOC 2.1.6'
+PACKAGE_VERSION='2.1.7'
+PACKAGE_STRING='OOC 2.1.7'
 PACKAGE_BUGREPORT='[email protected]'
 
 ac_unique_file="src/OOC/Parser.Mod"
@@ -780,7 +780,7 @@ if test "$ac_init_help" = "long"; then
   # Omit some internal or obsolete options to make the list less imposing.
   # This message is too long to be a string in the A/UX 3.1 sh.
   cat <<_ACEOF
-\`configure' configures OOC 2.1.6 to adapt to many kinds of systems.
+\`configure' configures OOC 2.1.7 to adapt to many kinds of systems.
 
 Usage: $0 [OPTION]... [VAR=VALUE]...
 
@@ -837,7 +837,7 @@ fi
 
 if test -n "$ac_init_help"; then
   case $ac_init_help in
-     short | recursive ) echo "Configuration of OOC 2.1.6:";;
+     short | recursive ) echo "Configuration of OOC 2.1.7:";;
    esac
   cat <<\_ACEOF
 
@@ -955,7 +955,7 @@ fi
 test -n "$ac_init_help" && exit 0
 if $ac_init_version; then
   cat <<\_ACEOF
-OOC configure 2.1.6
+OOC configure 2.1.7
 generated by GNU Autoconf 2.59
 
 Copyright (C) 2003 Free Software Foundation, Inc.
@@ -969,7 +969,7 @@ cat >&5 <<_ACEOF
 This file contains any messages produced by compilers while
 running configure, to aid debugging if configure makes a mistake.
 
-It was created by OOC $as_me 2.1.6, which was
+It was created by OOC $as_me 2.1.7, which was
 generated by GNU Autoconf 2.59.  Invocation command line was
 
   $ $0 $@
@@ -6359,7 +6359,7 @@ _ASBOX
 } >&5
 cat >&5 <<_CSEOF
 
-This file was extended by OOC $as_me 2.1.6, which was
+This file was extended by OOC $as_me 2.1.7, which was
 generated by GNU Autoconf 2.59.  Invocation command line was
 
   CONFIG_FILES    = $CONFIG_FILES
@@ -6419,7 +6419,7 @@ _ACEOF
 
 cat >>$CONFIG_STATUS <<_ACEOF
 ac_cs_version="\\
-OOC config.status 2.1.6
+OOC config.status 2.1.7
 configured by $0, generated by GNU Autoconf 2.59,
   with options \\"`echo "$ac_configure_args" | sed 's/[\\""\`\$]/\\\\&/g'`\\"
 

configure.ac

@@ -1,6 +1,6 @@
 dnl Autoconf requirements
 AC_PREREQ(2.53)
-AC_INIT(OOC,2.1.6,[email protected])
+AC_INIT(OOC,2.1.7,[email protected])
 AC_CONFIG_SRCDIR(src/OOC/Parser.Mod)
 AC_CONFIG_HEADER(lib/src/__config.h)
 

lib/pkginfo.xml.in

@@ -17,7 +17,7 @@
   </pragmas>
 
   <library name="oo2c" main-module="liboo2c">
-    <version current="2" revision="0" age="0"/>
+    <version current="3" revision="0" age="0"/>
   </library>
 
   <file-set source-dir="src">