fixes for parallel make, re-added the lost README files in mysql-test

BUILD/compile-pentium

+AM_MAKEFLAGS="-j 2"
 make -k clean
 /bin/rm -f */.deps/*.P config.cache
 

BUILD/compile-pentium-debug

+AM_MAKEFLAGS="-j 2"
 make -k clean
 /bin/rm -f */.deps/*.P config.cache
 

BUILD/compile-pentium-gcov

+AM_MAKEFLAGS="-j 2"
 make -k clean
 /bin/rm -f */.deps/*.P config.cache
 

Build-tools/Do-all-build-steps

@@ -10,7 +10,7 @@ to_host=`hostname`
 cc=gcc
 ccc=gcc
 EXTRA_CONFIG="--without-perl"
-
+AM_MAKEFLAGS="-j 2"
 echo "Building on $to_host"
 
 rm -rf $BD/*
@@ -34,7 +34,7 @@ umask 002
 CC=$cc CXX=$ccc 
 export CC CXX
 
-gmake -k distclean
+gmake -j 2 -k distclean
 rm -f NEW-RPMS/*
 
 # Stop on error
@@ -61,9 +61,9 @@ aclocal; autoheader; aclocal; automake; autoconf
  --enable-thread-safe-client \
  --without-berkeley-db
 
-gmake -j 2 # --jobs=4 does not work.
+gmake -j 2 .
 
-time gmake distcheck \
+time gmake -j 2 distcheck \
  EXTRA_CONF_ARGS="--with-unix-socket-path=/var/tmp/mysql.sock --with-low-memory $EXTRA_CONFIG"
 
 sh $BD/Build-tools/Do-rpm

Build-tools/Do-rpm

@@ -19,6 +19,7 @@ DBD_MYSQL_VERSION="1.2209"
 MAKERPM="$rpmdir/SOURCES/makerpm.pl"
 
 #######################
+AM_MAKEFLAGS="-j 2"
 
 VER=`grep "AM_INIT_AUTOMAKE(mysql, " $bpath/configure.in | \
  sed -e 's;AM_INIT_AUTOMAKE(mysql, ;;' -e 's;);;'`

mysql-test/README

+This directory contains a test suite for mysql daemon. To run
+the currently existing test cases, simply execute ./mysql-test-run in
+this directory. It will fire up the newly built mysqld and test it.
+Note that you do not have to have to do make install, and you could
+actually have a co-existing MySQL installation - the tests will not
+conflict with it.
+
+All tests must pass. If one or more of them fail on your system, please
+report the details to bugs@lists.mysql.com
+
+You can create your own test cases. To create a test case:
+
+ cd t
+ vi test_case_name.test
+
+ in the file, put a set of SQL commands that will create some tables,
+ load test data, run some queries to manipulate it.
+
+ then do ./mysql-test-run -record test_case_name
+ and look at r/test_case_name.result - edit the result if necessary. If you
+ have to edit it, you have found a bug.
+
+To submit your test case, put your .test file and .result file(s) into
+a tar.gz archive, add a README that explains the problem, ftp the 
+archive to ftp://support.mysql.com/pub/mysql/secret/ and send  a mail
+to bugs@lists.mysql.com
+
+
+

mysql-test/README.gcov

+To be able to see the level of coverage with the current test suite,
+do the following:
+
+  - make sure gcov is installed
+  - compile with BUILD/compile-pentium-gcov ( if your machine is not pentium, hack
+this script, or just live with the pentium-specific stuff)
+  - ./mysql-test-run -gcov
+  - to see the level of coverage for a given source file:
+     grep source_file_name /tmp/gcov.out
+  - to see which lines are not yet covered, look at source_file_name.gcov in the source tree. Then think hard about a test case that will cover those
+lines, and write one!