--- embedaddon/pcre/config.h.in	2012/02/21 23:05:51	1.1.1.1
+++ embedaddon/pcre/config.h.in	2012/02/21 23:50:25	1.1.1.2
@@ -30,8 +30,8 @@ them both to 0; an emulation function will be used. */
    character codes, define this macro as 1. On systems that can use
    "configure", this can be done via --enable-ebcdic. PCRE will then assume
    that all input strings are in EBCDIC. If you do not define this macro, PCRE
-   will assume input strings are ASCII or UTF-8 Unicode. It is not possible to
-   build a version of PCRE that supports both EBCDIC and UTF-8. */
+   will assume input strings are ASCII or UTF-8/16 Unicode. It is not possible
+   to build a version of PCRE that supports both EBCDIC and UTF-8/16. */
 #undef EBCDIC
 
 /* Define to 1 if you have the `bcopy' function. */
@@ -250,17 +250,23 @@ them both to 0; an emulation function will be used. */
    handle .gz files. */
 #undef SUPPORT_LIBZ
 
+/* Define to enable the 16 bit PCRE library. */
+#undef SUPPORT_PCRE16
+
+/* Define to enable the 8 bit PCRE library. */
+#undef SUPPORT_PCRE8
+
 /* Define to enable JIT support in pcregrep. */
 #undef SUPPORT_PCREGREP_JIT
 
 /* Define to enable support for Unicode properties. */
 #undef SUPPORT_UCP
 
-/* Define to enable support for the UTF-8 Unicode encoding. This will work
+/* Define to enable support for the UTF-8/16 Unicode encoding. This will work
    even in an EBCDIC environment, but it is incompatible with the EBCDIC
-   macro. That is, PCRE can support *either* EBCDIC code *or* ASCII/UTF-8, but
-   not both at once. */
-#undef SUPPORT_UTF8
+   macro. That is, PCRE can support *either* EBCDIC code *or* ASCII/UTF-8/16,
+   but not both at once. */
+#undef SUPPORT_UTF
 
 /* Version number of package */
 #undef VERSION