Index: general/prog/cmake.xml
===================================================================
--- general/prog/cmake.xml	(revision 1c159417e37196bda3d1ef19d2902463a2ef67bd)
+++ general/prog/cmake.xml	(revision 39e42c88687a7c23e119e98e2999e4855322344c)
@@ -7,8 +7,8 @@
   <!ENTITY cmake-download-http "http://www.cmake.org/files/v&cmake-major-version;/cmake-&cmake-version;.tar.gz">
   <!ENTITY cmake-download-ftp  " ">
-  <!ENTITY cmake-md5sum        "4cb3ff35b2472aae70f542116d616e63">
+  <!ENTITY cmake-md5sum        "33c5d09d4c33d4ffcc63578a6ba8777e">
   <!ENTITY cmake-size          "6.5 MB">
-  <!ENTITY cmake-buildsize     "704 MB (with tests and cmake-gui)">
-  <!ENTITY cmake-time          "4 SBU, with parallelism = 4 (with tests and cmake-gui)">
+  <!ENTITY cmake-buildsize     "346 MB (648 MB with tests and cmake-gui)">
+  <!ENTITY cmake-time          "4.2 SBU (12.1 SBU with tests and cmake-gui)">
 ]>
 
@@ -124,10 +124,10 @@
       <replaceable>&lt;N&gt;</replaceable> is an integer between 1 and the
       number of system cores. For some systems, it may be necessary to run the
-      tests only for Qt4 using <command>source setq4</command>, then
-      <command>export CXXFLAGS="-std=c++11"</command> before the
-      <command>./bootstrap ...</command>) command.  If used, be sure to
-      <command>unset CXXFLAGS</command> after the tests.  One of the problematic
-      tests relates to the test procedures finding the correct Qt files. Eight
-      of 447 tests are known to fail under some circumstances related to Gtk+2
+      tests only for Qt4 using <command>source setq4</command>
+      before the
+      <command>./bootstrap ...</command>) command.  
+      One of the problematic
+      tests relates to the test procedures finding the correct Qt files. One
+      of 444 tests is known to fail under some circumstances related to Gtk+2
       and c++ standards.
 
Index: general/prog/dbus-python.xml
===================================================================
--- general/prog/dbus-python.xml	(revision 1c159417e37196bda3d1ef19d2902463a2ef67bd)
+++ general/prog/dbus-python.xml	(revision 39e42c88687a7c23e119e98e2999e4855322344c)
@@ -7,8 +7,8 @@
   <!ENTITY dbus-python-download-http "http://dbus.freedesktop.org/releases/dbus-python/dbus-python-&dbus-python-version;.tar.gz">
   <!ENTITY dbus-python-download-ftp  " ">
-  <!ENTITY dbus-python-md5sum        "b09cd2d1a057cc432ce944de3fc06bf7">
-  <!ENTITY dbus-python-size          "592 KB">
-  <!ENTITY dbus-python-buildsize     "11 MB">
-  <!ENTITY dbus-python-time          "0.3 SBU">
+  <!ENTITY dbus-python-md5sum        "7372a588c83a7232b4e08159bfd48fe5">
+  <!ENTITY dbus-python-size          "600 KB">
+  <!ENTITY dbus-python-buildsize     "9.3 MB (both versions with tests)">
+  <!ENTITY dbus-python-time          "0.4 SBU (both versions with tests)">
 ]>
 
Index: general/prog/gdb.xml
===================================================================
--- general/prog/gdb.xml	(revision 1c159417e37196bda3d1ef19d2902463a2ef67bd)
+++ general/prog/gdb.xml	(revision 39e42c88687a7c23e119e98e2999e4855322344c)
@@ -7,8 +7,8 @@
   <!ENTITY gdb-download-http "https://ftp.gnu.org/gnu/gdb/gdb-&gdb-version;.tar.xz">
   <!ENTITY gdb-download-ftp  "ftp://ftp.gnu.org/gnu/gdb/gdb-&gdb-version;.tar.xz">
-  <!ENTITY gdb-md5sum        "39e654460c9cdd80200a29ac020cfe11">
+  <!ENTITY gdb-md5sum        "b5c784685e1cde65ba135feea86b6d75">
   <!ENTITY gdb-size          "18 MB">
-  <!ENTITY gdb-buildsize     "419 MB (additional 349 MB for tests)">
-  <!ENTITY gdb-time          "2.4 SBU (add up to 7.8 SBU for tests)">
+  <!ENTITY gdb-buildsize     "399 MB (additional 173 MB for tests, additional 1.3 GB for documentation)">
+  <!ENTITY gdb-time          "2.6 SBU (add up to 13 SBU for tests)">
 ]>
 
@@ -124,17 +124,60 @@
       See <emphasis>gdb/testsuite/README</emphasis> and <ulink
       url="https://sourceware.org/gdb/wiki/TestingGDB">TestingGDB</ulink>.
-      There are many problems with the test suite. First one is that you need
-      to clean some directories, if re-running the tests. For that reason, it
-      is recommended to make a copy of the compiled source code directory,
-      before the tests, in case you need to run the tests again. Results depend
-      on installed compilers, there are differences if run locally or remotely,
-      a large number of timeouts (there is a variable that can be set to
-      increase time for timeout, but changing it, apparently the total number
-      of tests is not conserved), there are failures associated with system
-      readline 6.x, between others. A few tests assume that the header file
-      <filename>&lt;sys/sdt.h&gt;</filename>, part of <ulink
-      url="https://sourceware.org/systemtap/">SystemTap</ulink>, is present.
-      Unexpected failures are less than 0.3%.
-    </para>
+      There are many problems with the test suite:
+    </para>
+      
+    <itemizedlist>
+      <listitem>
+        <para>
+          Clean directories ire needed if re-running the tests.  For that
+          reason, it is recommended to make a copy of the compiled source code
+          directory before the tests in case you need to run the tests again. 
+        </para>
+      </listitem>
+        
+      <listitem>
+        <para>
+          Results depend on installed compilers.
+        </para>
+      </listitem>
+        
+      <listitem>
+        <para>
+          If run remotely over an ssh connection, the tests will hang 
+          and require a hard (power cycle) reset of the sytem.
+        </para>
+      </listitem>
+        
+      <listitem>
+        <para>
+          There are a large number of timeouts (there is a variable 
+          that can be set to increase time for timeout, but 
+          changing it will result in a different number of tests being 
+          run.
+        </para>
+      </listitem>
+        
+      <listitem>
+        <para>
+          There are failures associated with system readline 6.x.
+        </para>
+      </listitem>
+        
+      <listitem>
+        <para>
+          A few tests assume that the header file
+          <filename>&lt;sys/sdt.h&gt;</filename>, part of <ulink
+          url="https://sourceware.org/systemtap/">SystemTap</ulink>, is
+          present.
+        </para>
+      </listitem>
+        
+      <listitem>
+        <para>
+          About 3% of the tests fail (out of over 35000 tests). 
+        </para>
+      </listitem>
+        
+    </itemizedlist>
 
     <para>
