RubyGems - gtk2 - Versions diffs - 0.90.2-x86-mingw32 → 0.90.3-x86-mingw32 - Mend

gtk2 0.90.2-x86-mingw32 → 0.90.3-x86-mingw32

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (1536) hide show

data/vendor/local/share/gtk-doc/html/glib/glib-building.html CHANGED

@@ -8,7 +8,7 @@
 <link rel="up" href="glib.html" title="GLib Overview">
 <link rel="prev" href="glib.html" title="GLib Overview">
 <link rel="next" href="glib-cross-compiling.html" title="Cross-compiling the GLib package">
-<meta name="generator" content="GTK-Doc V1.14 (XML mode)">
+<meta name="generator" content="GTK-Doc V1.15.1 (XML mode)">
 <link rel="stylesheet" href="style.css" type="text/css">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -19,7 +19,7 @@
 <th width="100%" align="center">GLib Reference Manual</th>
 <td><a accesskey="n" href="glib-cross-compiling.html"><img src="right.png" width="24" height="24" border="0" alt="Next"></a></td>
 </tr></table>
-<div class="refentry" title="Compiling the GLib package">
+<div class="refentry">
 <a name="glib-building"></a><div class="titlepage"></div>
 <div class="refnamediv"><table width="100%"><tr>
 <td valign="top">
@@ -30,7 +30,7 @@ How to compile GLib itself
 </td>
 <td valign="top" align="right"></td>
 </tr></table></div>
-<div class="refsect1" title="Building the Library on UNIX">
+<div class="refsect1">
 <a name="building"></a><h2>Building the Library on UNIX</h2>
 <p>
         On UNIX, GLib uses the standard GNU build system,
@@ -64,7 +64,7 @@ How to compile GLib itself
 	about the build process and ways to influence it.
       </p>
 </div>
-<div class="refsect1" title="Dependencies">
+<div class="refsect1">
 <a name="dependencies"></a><h2>Dependencies</h2>
 <p>
         Before you can compile the GLib library, you need to have
@@ -175,9 +175,18 @@ How to compile GLib itself
           GLib without SELinux support, use the
           <code class="option">--disable-selinux</code> configure option.
         </p></li>
+<li class="listitem"><p>
+          The optional support for DTrace requires the <code class="filename">sys/sdt.h</code> header,
+          which is provided by SystemTap on Linux.  To build GLib without DTrace, use the
+          <code class="option">--disable-dtrace</code> configure option.
+        </p></li>
+<li class="listitem"><p>
+          The optional support for <a class="ulink" href="http://sourceware.org/systemtap/" target="_top">SystemTap</a> can be disabled with the
+          <code class="option">--disable-systemtap</code> configure option.
+        </p></li>
 </ul></div>
 </div>
-<div class="refsect1" title="Extra Configuration Options">
+<div class="refsect1">
 <a name="extra-configuration-options"></a><h2>Extra Configuration Options</h2>
 <p>
         In addition to the normal options, the
@@ -185,10 +194,10 @@ How to compile GLib itself
         library supports these additional arguments:
         </p>
-<div class="cmdsynopsis"><p><code class="command">configure</code>  [[--enable-debug=[no|minimum|yes]]] [[--disable-gc-friendly] |  [--enable-gc-friendly]] [[--disable-mem-pools] |  [--enable-mem-pools]] [[--disable-threads] |  [--enable-threads]] [[--with-threads=[none|posix|dce|win32]]] [[--disable-regex] |  [--enable-regex]] [[--with-pcre=[internal|system]]] [[--disable-included-printf] |  [--enable-included-printf]] [[--disable-visibility] |  [--enable-visibility]] [[--disable-gtk-doc] |  [--enable-gtk-doc]] [[--disable-man] |  [--enable-man]] [[--disable-xattr] |  [--enable-xattr]] [[--disable-selinux] |  [--enable-selinux]] [[--with-runtime-libdir=RELPATH]]</p></div>
+<div class="cmdsynopsis"><p><code class="command">configure</code>  [[--enable-debug=[no|minimum|yes]]] [[--disable-gc-friendly] |  [--enable-gc-friendly]] [[--disable-mem-pools] |  [--enable-mem-pools]] [[--disable-threads] |  [--enable-threads]] [[--with-threads=[none|posix|dce|win32]]] [[--disable-regex] |  [--enable-regex]] [[--with-pcre=[internal|system]]] [[--disable-included-printf] |  [--enable-included-printf]] [[--disable-visibility] |  [--enable-visibility]] [[--disable-gtk-doc] |  [--enable-gtk-doc]] [[--disable-man] |  [--enable-man]] [[--disable-xattr] |  [--enable-xattr]] [[--disable-selinux] |  [--enable-selinux]] [[--disable-dtrace] |  [--enable-dtrace]] [[--disable-systemtap] |  [--enable-systemtap]] [[--enable-gcov] |  [--disable-gcov]] [[--with-runtime-libdir=RELPATH]]</p></div>
 <p>
       </p>
-<p title="--enable-debug"><b><code class="systemitem">--enable-debug</code>. </b>
+<p><b><code class="systemitem">--enable-debug</code>. </b>
          Turns on various amounts of debugging support. Setting this to 'no'
          disables g_assert(), g_return_if_fail(), g_return_val_if_fail() and
          all cast checks between different object types. Setting it to 'minimum'         disables only cast checks. Setting it to 'yes' enables
@@ -200,7 +209,7 @@ How to compile GLib itself
          <code class="option">--enable-debug=no</code> should <span class="emphasis"><em>not</em></span>
          be used for stable releases of GLib.
         </p>
-<p title="--disable-gc-friendly and --enable-gc-friendly"><b><code class="systemitem">--disable-gc-friendly</code> and
+<p><b><code class="systemitem">--disable-gc-friendly</code> and
           <code class="systemitem">--enable-gc-friendly</code>. </b>
 	  By default, and with <code class="systemitem">--disable-gc-friendly</code>
 	  as well, Glib does not clear the memory for certain objects before they
@@ -241,7 +250,7 @@ How to compile GLib itself
         Since clearing the memory has a cost,
         <code class="systemitem">--disable-gc-friendly</code> is the default.
       </p>
-<p title="--disable-mem-pools and --enable-mem-pools"><b><code class="systemitem">--disable-mem-pools</code> and
+<p><b><code class="systemitem">--disable-mem-pools</code> and
           <code class="systemitem">--enable-mem-pools</code>. </b>
         Many small chunks of memory are often allocated via collective pools
         in GLib and are cached after release to speed up reallocations.
@@ -277,16 +286,16 @@ How to compile GLib itself
          <code class="literal">G_BSEARCH_ALIGN_POWER2</code> becomes non-functional
         </p></li>
 </ul></div>
-<p title="--disable-mem-pools and --enable-mem-pools">
+<p>
       </p>
-<p title="--disable-threads and --enable-threads"><b><code class="systemitem">--disable-threads</code> and
+<p><b><code class="systemitem">--disable-threads</code> and
           <code class="systemitem">--enable-threads</code>. </b>
            Do not compile GLib to be multi thread safe. GLib
            will be slightly faster then. This is however not
            recommended, as many programs rely on GLib being
            multi thread safe.
         </p>
-<p title="--with-threads"><b><code class="systemitem">--with-threads</code>. </b>
+<p><b><code class="systemitem">--with-threads</code>. </b>
           Specify a thread implementation to use.
           </p>
 <div class="itemizedlist"><ul class="itemizedlist" type="disc">
@@ -303,17 +312,17 @@ How to compile GLib itself
                 <code class="function">g_thread_init()</code> by the programmer.
               </p></li>
 </ul></div>
-<p title="--with-threads">
+<p>
         </p>
-<p title="--disable-regex and --enable-regex"><b><code class="systemitem">--disable-regex</code> and
+<p><b><code class="systemitem">--disable-regex</code> and
           <code class="systemitem">--enable-regex</code>. </b>
            Do not compile GLib with regular expression support.
            GLib will be smaller because it will not need the
            PCRE library. This is however not recommended, as
            programs may need GRegex.
         </p>
-<p title="--with-pcre"><b><code class="systemitem">--with-pcre</code>. </b>
+<p><b><code class="systemitem">--with-pcre</code>. </b>
           Specify whether to use the internal or the system-supplied
           PCRE library.
           </p>
@@ -327,7 +336,7 @@ How to compile GLib itself
               the system-supplied PCRE library.
             </p></li>
 </ul></div>
-<p title="--with-pcre">
+<p>
           Using the internal PCRE is the preferred solution:
           </p>
 <div class="itemizedlist"><ul class="itemizedlist" type="disc">
@@ -346,9 +355,9 @@ How to compile GLib itself
                 this variables could lead to problems when they are modified.
               </p></li>
 </ul></div>
-<p title="--with-pcre">
+<p>
         </p>
-<p title="--disable-included-printf and --enable-included-printf"><b><code class="systemitem">--disable-included-printf</code> and
+<p><b><code class="systemitem">--disable-included-printf</code> and
            <code class="systemitem">--enable-included-printf</code>. </b>
           By default the <span class="command"><strong>configure</strong></span> script will try
           to auto-detect whether the C library provides a suitable set
@@ -363,7 +372,7 @@ How to compile GLib itself
           an implementation fo the <code class="function">printf()</code> family
           should be included or not.
         </p>
-<p title="--disable-visibility and --enable-visibility"><b><code class="systemitem">--disable-visibility</code> and
+<p><b><code class="systemitem">--disable-visibility</code> and
            <code class="systemitem">--enable-visibility</code>. </b>
           By default, GLib uses ELF visibility attributes to optimize
           PLT table entries if the compiler supports ELF visibility
@@ -375,7 +384,7 @@ How to compile GLib itself
           visibility attributes. The <code class="option">--disable-visibility</code>
           option allows to do that.
         </p>
-<p title="--disable-gtk-doc and --enable-gtk-doc"><b><code class="systemitem">--disable-gtk-doc</code> and
+<p><b><code class="systemitem">--disable-gtk-doc</code> and
           <code class="systemitem">--enable-gtk-doc</code>. </b>
           By default the <span class="command"><strong>configure</strong></span> script will try
           to auto-detect whether the
@@ -388,7 +397,7 @@ How to compile GLib itself
           pre-generated HTML files will be installed instead of
           building them on your machine.
         </p>
-<p title="--disable-man and --enable-man"><b><code class="systemitem">--disable-man</code> and
+<p><b><code class="systemitem">--disable-man</code> and
           <code class="systemitem">--enable-man</code>. </b>
           By default the <span class="command"><strong>configure</strong></span> script will try
           to auto-detect whether <span class="application">xsltproc</span>
@@ -399,7 +408,7 @@ How to compile GLib itself
           used or not. The distribution includes pre-generated man
           pages.
         </p>
-<p title="--disable-xattr and --enable-xattr"><b><code class="systemitem">--disable-xattr</code> and
+<p><b><code class="systemitem">--disable-xattr</code> and
           <code class="systemitem">--enable-xattr</code>. </b>
           By default the <span class="command"><strong>configure</strong></span> script will try
           to auto-detect whether the getxattr() family of functions
@@ -409,7 +418,7 @@ How to compile GLib itself
           should be included or not. getxattr() and friends can
           be provided by glibc or by the standalone libattr library.
         </p>
-<p title="--disable-selinux and --enable-selinux"><b><code class="systemitem">--disable-selinux</code> and
+<p><b><code class="systemitem">--disable-selinux</code> and
           <code class="systemitem">--enable-selinux</code>. </b>
           By default the <span class="command"><strong>configure</strong></span> script will
           auto-detect if libselinux is available and include
@@ -417,7 +426,26 @@ How to compile GLib itself
           used to explicitly control whether SELinux support should
 	  be included.
         </p>
-<p title="--with-runtime-libdir=RELPATH"><b><code class="systemitem">--with-runtime-libdir=RELPATH</code>. </b>
+<p><b><code class="systemitem">--disable-dtrace</code> and
+          <code class="systemitem">--enable-dtrace</code>. </b>
+          By default the <span class="command"><strong>configure</strong></span> script will
+          detect if DTrace support is available, and use it.
+        </p>
+<p><b><code class="systemitem">--disable-systemtap</code> and
+          <code class="systemitem">--enable-systemtap</code>. </b>
+          This option requires DTrace support.  If it is available, then
+	  the <span class="command"><strong>configure</strong></span> script will also check for
+	  the presence of SystemTap.
+        </p>
+<p><b><code class="systemitem">--enable-gcov</code> and
+          <code class="systemitem">--disable-gcov</code>. </b>
+          Enable the generation of coverage reports for the GLib tests.
+          This requires the lcov frontend to gcov from the
+          <a class="ulink" href="http://ltp.sourceforge.net" target="_top">Linux Test Project</a>.
+          To generate a coverage report, use the lcov make target. The
+          report is placed in the <code class="filename">glib-lcov</code> directory.
+        </p>
+<p><b><code class="systemitem">--with-runtime-libdir=RELPATH</code>. </b>
           Allows specifying a relative path to where to install the runtime
           libraries (meaning library files used for running, not developing,
           GLib applications). This can be used in operating system setups where
@@ -433,6 +461,6 @@ How to compile GLib itself
 </div>
 <div class="footer">
 <hr>
-          Generated by GTK-Doc V1.14</div>
+          Generated by GTK-Doc V1.15.1</div>
 </body>
 </html>

data/vendor/local/share/gtk-doc/html/glib/glib-changes.html CHANGED

@@ -8,7 +8,7 @@
 <link rel="up" href="glib.html" title="GLib Overview">
 <link rel="prev" href="glib-running.html" title="Running GLib Applications">
 <link rel="next" href="glib-regex-syntax.html" title="Regular expression syntax">
-<meta name="generator" content="GTK-Doc V1.14 (XML mode)">
+<meta name="generator" content="GTK-Doc V1.15.1 (XML mode)">
 <link rel="stylesheet" href="style.css" type="text/css">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -19,7 +19,7 @@
 <th width="100%" align="center">GLib Reference Manual</th>
 <td><a accesskey="n" href="glib-regex-syntax.html"><img src="right.png" width="24" height="24" border="0" alt="Next"></a></td>
 </tr></table>
-<div class="refentry" title="Changes to GLib">
+<div class="refentry">
 <a name="glib-changes"></a><div class="titlepage"></div>
 <div class="refnamediv"><table width="100%"><tr>
 <td valign="top">
@@ -30,8 +30,8 @@ Incompatible changes made between successing versions of GLib
 </td>
 <td valign="top" align="right"></td>
 </tr></table></div>
-<div class="refsect1" title="Incompatible changes from 2.0 to 2.2">
-<a name="id520879"></a><h2>Incompatible changes from 2.0 to 2.2</h2>
+<div class="refsect1">
+<a name="id561689"></a><h2>Incompatible changes from 2.0 to 2.2</h2>
 <div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">
 <p>
 GLib changed the seeding algorithm for the pseudo-random number
@@ -55,8 +55,8 @@ with Glib-2.0 that you need to reproduce exactly.
 </p>
 </li></ul></div>
 </div>
-<div class="refsect1" title="Incompatible changes from 1.2 to 2.0">
-<a name="id520935"></a><h2>Incompatible changes from 1.2 to 2.0</h2>
+<div class="refsect1">
+<a name="id537002"></a><h2>Incompatible changes from 1.2 to 2.0</h2>
 <p>
 The <a class="ulink" href="http://developer.gnome.org/dotplan/porting/" target="_top">GNOME 2.0
 porting guide</a> on <a class="ulink" href="http://developer.gnome.org" target="_top">http://developer.gnome.org</a>
@@ -154,6 +154,6 @@ Deprecated functions that got removed:
 </div>
 <div class="footer">
 <hr>
-          Generated by GTK-Doc V1.14</div>
+          Generated by GTK-Doc V1.15.1</div>
 </body>
 </html>

data/vendor/local/share/gtk-doc/html/glib/glib-compiling.html CHANGED

@@ -8,7 +8,7 @@
 <link rel="up" href="glib.html" title="GLib Overview">
 <link rel="prev" href="glib-cross-compiling.html" title="Cross-compiling the GLib package">
 <link rel="next" href="glib-running.html" title="Running GLib Applications">
-<meta name="generator" content="GTK-Doc V1.14 (XML mode)">
+<meta name="generator" content="GTK-Doc V1.15.1 (XML mode)">
 <link rel="stylesheet" href="style.css" type="text/css">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -19,7 +19,7 @@
 <th width="100%" align="center">GLib Reference Manual</th>
 <td><a accesskey="n" href="glib-running.html"><img src="right.png" width="24" height="24" border="0" alt="Next"></a></td>
 </tr></table>
-<div class="refentry" title="Compiling GLib Applications">
+<div class="refentry">
 <a name="glib-compiling"></a><div class="titlepage"></div>
 <div class="refnamediv"><table width="100%"><tr>
 <td valign="top">
@@ -30,8 +30,8 @@ How to compile your GLib application
 </td>
 <td valign="top" align="right"></td>
 </tr></table></div>
-<div class="refsect1" title="Compiling GLib Applications on UNIX">
-<a name="id528895"></a><h2>Compiling GLib Applications on UNIX</h2>
+<div class="refsect1">
+<a name="id557847"></a><h2>Compiling GLib Applications on UNIX</h2>
 <p>
 To compile a GLib application, you need to tell the compiler where to
 find the GLib header files and libraries. This is done with the
@@ -113,6 +113,6 @@ by using the command line option <code class="literal">-DG_DISABLE_SINGLE_INCLUD
 </div>
 <div class="footer">
 <hr>
-          Generated by GTK-Doc V1.14</div>
+          Generated by GTK-Doc V1.15.1</div>
 </body>
 </html>

data/vendor/local/share/gtk-doc/html/glib/glib-core.html CHANGED

@@ -8,7 +8,7 @@
 <link rel="up" href="index.html" title="GLib Reference Manual">
 <link rel="prev" href="glib-Atomic-Operations.html" title="Atomic Operations">
 <link rel="next" href="glib-The-Main-Event-Loop.html" title="The Main Event Loop">
-<meta name="generator" content="GTK-Doc V1.14 (XML mode)">
+<meta name="generator" content="GTK-Doc V1.15.1 (XML mode)">
 <link rel="stylesheet" href="style.css" type="text/css">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -19,7 +19,7 @@
 <th width="100%" align="center">GLib Reference Manual</th>
 <td><a accesskey="n" href="glib-The-Main-Event-Loop.html"><img src="right.png" width="24" height="24" border="0" alt="Next"></a></td>
 </tr></table>
-<div class="chapter" title="GLib Core Application Support">
+<div class="chapter">
 <div class="titlepage"><div><div><h2 class="title">
 <a name="glib-core"></a>GLib Core Application Support</h2></div></div></div>
 <div class="toc"><dl>
@@ -59,6 +59,6 @@
 </div>
 <div class="footer">
 <hr>
-          Generated by GTK-Doc V1.14</div>
+          Generated by GTK-Doc V1.15.1</div>
 </body>
 </html>

data/vendor/local/share/gtk-doc/html/glib/glib-cross-compiling.html CHANGED

@@ -8,7 +8,7 @@
 <link rel="up" href="glib.html" title="GLib Overview">
 <link rel="prev" href="glib-building.html" title="Compiling the GLib package">
 <link rel="next" href="glib-compiling.html" title="Compiling GLib Applications">
-<meta name="generator" content="GTK-Doc V1.14 (XML mode)">
+<meta name="generator" content="GTK-Doc V1.15.1 (XML mode)">
 <link rel="stylesheet" href="style.css" type="text/css">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -19,7 +19,7 @@
 <th width="100%" align="center">GLib Reference Manual</th>
 <td><a accesskey="n" href="glib-compiling.html"><img src="right.png" width="24" height="24" border="0" alt="Next"></a></td>
 </tr></table>
-<div class="refentry" title="Cross-compiling the GLib package">
+<div class="refentry">
 <a name="glib-cross-compiling"></a><div class="titlepage"></div>
 <div class="refnamediv"><table width="100%"><tr>
 <td valign="top">
@@ -30,7 +30,7 @@ How to cross-compile GLib
 </td>
 <td valign="top" align="right"></td>
 </tr></table></div>
-<div class="refsect1" title="Building the Library for a different architecture">
+<div class="refsect1">
 <a name="cross"></a><h2>Building the Library for a different architecture</h2>
 <p>
         Cross-compilation is the process of compiling a program or
@@ -74,9 +74,9 @@ chmod a-w win32.cache   # prevent configure from changing it
          of these won't need to be set in most cases.
       </p>
 </div>
-<div class="refsect1" title="Cache file variables">
+<div class="refsect1">
 <a name="cache-file-variables"></a><h2>Cache file variables</h2>
-<p title="glib_cv_long_long_format=[ll/q/I64]"><b>glib_cv_long_long_format=[ll/q/I64]. </b>
+<p><b>glib_cv_long_long_format=[ll/q/I64]. </b>
            Format used by <code class="function">printf()</code> and
            <code class="function">scanf()</code> for 64 bit integers. "ll" is
            the C99 standard, and what is used by the 'trio' library
@@ -84,68 +84,68 @@ chmod a-w win32.cache   # prevent configure from changing it
            insufficiently capable.
            Doesn't need to be set if you are compiling using trio.
         </p>
-<p title="glib_cv_stack_grows=[yes/no]"><b>glib_cv_stack_grows=[yes/no]. </b>
+<p><b>glib_cv_stack_grows=[yes/no]. </b>
            Whether the stack grows up or down. Most places will want "no",
            A few architectures, such as PA-RISC need "yes".
         </p>
-<p title="glib_cv_working_bcopy=[yes/no]"><b>glib_cv_working_bcopy=[yes/no]. </b>
+<p><b>glib_cv_working_bcopy=[yes/no]. </b>
            Whether your <code class="function">bcopy()</code> can handle overlapping
            copies. Only needs to be set if you don't have
            <code class="function">memmove()</code>. (Very unlikely)
 	</p>
-<p title="glib_cv_sane_realloc=[yes/np]"><b>glib_cv_sane_realloc=[yes/np]. </b>
+<p><b>glib_cv_sane_realloc=[yes/np]. </b>
             Whether your <code class="function">realloc()</code> conforms to ANSI C
             and can handle <code class="literal">NULL</code> as the first argument.
             Defaults to "yes" and probably doesn't need to be set.
 	</p>
-<p title="glib_cv_have_strlcpy=[yes/no]"><b>glib_cv_have_strlcpy=[yes/no]. </b>
+<p><b>glib_cv_have_strlcpy=[yes/no]. </b>
             Whether you have <code class="function">strlcpy()</code> that matches
             OpenBSD. Defaults to "no", which is safe, since GLib uses a
             built-in version in that case.
 	</p>
-<p title="glib_cv_va_val_copy=[yes/no]"><b>glib_cv_va_val_copy=[yes/no]. </b>
+<p><b>glib_cv_va_val_copy=[yes/no]. </b>
             Whether <span class="type">va_list</span> can be copied as a pointer. If set
             to "no", then <code class="function">memcopy()</code> will be used. Only
             matters if you don't have <code class="function">va_copy()</code> or
             <code class="function">__va_copy()</code>. (So, doesn't matter for GCC.)
             Defaults to "yes" which is slightly more common than "no".
 	</p>
-<p title="glib_cv_rtldglobal_broken=[yes/no]"><b>glib_cv_rtldglobal_broken=[yes/no]. </b>
+<p><b>glib_cv_rtldglobal_broken=[yes/no]. </b>
             Whether you have a bug found in OSF/1 v5.0. Defaults to "no".
          </p>
-<p title="glib_cv_uscore=[yes/no]"><b>glib_cv_uscore=[yes/no]. </b>
+<p><b>glib_cv_uscore=[yes/no]. </b>
             Whether an underscore needs to be prepended to symbols when
             looking them up via <code class="function">dlsym()</code>. Only needs to
             be set if your system uses
 	    <code class="function">dlopen()</code>/<code class="function">dlsym()</code>.
 	 </p>
-<p title="ac_cv_func_posix_getpwuid_r=[yes/no]"><b>ac_cv_func_posix_getpwuid_r=[yes/no]. </b>
+<p><b>ac_cv_func_posix_getpwuid_r=[yes/no]. </b>
             Whether you have a getpwuid_r function (in your C library,
 	    not your thread library) that conforms to the POSIX spec.
             (Takes a 'struct passwd **' as the final argument)
          </p>
-<p title="ac_cv_func_nonposix_getpwuid_r=[yes/no]"><b>ac_cv_func_nonposix_getpwuid_r=[yes/no]. </b>
+<p><b>ac_cv_func_nonposix_getpwuid_r=[yes/no]. </b>
             Whether you have some variant of <code class="function">getpwuid_r()</code>
             that doesn't conform to to the POSIX spec, but GLib might be able
             to use (or might segfault.) Only needs to be set if
 	    <code class="literal">ac_cv_func_posix_getpwuid_r</code> is not set. It's
             safest to set this to "no".
          </p>
-<p title="ac_cv_func_posix_getgrgid_r=[yes/no]"><b>ac_cv_func_posix_getgrgid_r=[yes/no]. </b>
+<p><b>ac_cv_func_posix_getgrgid_r=[yes/no]. </b>
             Whether you have a getgrgid_r function that conforms to
             the POSIX spec.
          </p>
-<p title="glib_cv_use_pid_surrogate=[yes/no]"><b>glib_cv_use_pid_surrogate=[yes/no]. </b>
+<p><b>glib_cv_use_pid_surrogate=[yes/no]. </b>
             Whether to use a <code class="function">setpriority()</code> on the PID of
             the thread as a method for setting the priority of threads. This
             only needs to be set when using POSIX threads.
          </p>
-<p title="ac_cv_func_printf_unix98=[yes/no]"><b>ac_cv_func_printf_unix98=[yes/no]. </b>
+<p><b>ac_cv_func_printf_unix98=[yes/no]. </b>
            Whether your <code class="function">printf()</code> family supports Unix98
            style <code class="literal">%N$</code> positional parameters. Defaults to
 	"no".
          </p>
-<p title="ac_cv_func_vsnprintf_c99=[yes/no]"><b>ac_cv_func_vsnprintf_c99=[yes/no]. </b>
+<p><b>ac_cv_func_vsnprintf_c99=[yes/no]. </b>
             Whether you have a <code class="function">vsnprintf()</code> with C99
             semantics. (C99 semantics means returning the number of bytes
             that would have been written had the output buffer had enough
@@ -155,6 +155,6 @@ chmod a-w win32.cache   # prevent configure from changing it
 </div>
 <div class="footer">
 <hr>
-          Generated by GTK-Doc V1.14</div>
+          Generated by GTK-Doc V1.15.1</div>
 </body>
 </html>