unnecessarily.  Most prominently, no longer re-run 'tar xf &&
configure' every benchmark run.  Instead, if configure was
successfully executed last benchmark run, just do 'make clean'.  This
is equivalent to what we do now between build runs, when the
repeat-count is > 1.

This feature is not turned on by default, but must be enabled with the
new --force=0 flag.  --force=1 keeps the same behavior as before: we
always re-run configure in each build-directory.  --force=2 adds more
repeat-work than before; in --force=2 mode, we always re-download the
package from the web, even if we had successfully downloaded it
before.

Note that the 'tar' command currently warms the file-cache, which
makes build times more consistent, so there is so cost to setting
--force=0, in terms of the data collected.

Reviewed by klarlund

This makes the linux kernel build with pump-mode when the benchmark script is
used.

Also, include the '-t' option to the include server; that prints out the elapsed
and CPU times at the end of the build.

REVIEW: csilvers@google.com
TESTS: (on quad-cpu workstation)
      DISTCC_HOSTS="--randomize `/home/klarlund/svn-distcc/distcc/lsdistcc -P1 -k100 -d`" PATH=`pwd`:$PATH bench/benchmark.py --cc='/usr/crosstool/v10/gcc-4.2.1-glibc-2.3.2/x86_64-unknown-linux-gnu/bin/x86_64-unknown-linux-gnu-gcc' --cxx='void' -n 5 -c 'pump,h40,j120' -c 'dist,h40,j32' linux-2.6.25

project               compiler                             time      s.d.
linux-2.6.25          pump_h39_j120                    69.6525s    3.0969s
linux-2.6.25          dist_h39_j32                    103.8416s   10.8041s

(typically the only change is in the FSF street address).  Add Google
copyright line in some places it was missing.  Add GPLv2 notice to
avahi patches.

OKed by fergus

Get rid of source_name, which isn't used anywhere.

Also, add a few more benchmark projects.  These are big(ish) and
written in C++, to test distcc on C++ code.

Reviewed by klarlund@google.com

directory up to the top level: delete the distcc directory (I already
copied it all to the top level in my last commit).

This requires changing all files that refer to distcc/FOO to refer
directly to FOO instead.  Mostly this is Makefile.in and setup.py, but
there are a few other changes in scripts that have to hard-code paths,
like configure.ac and pump.in.  Also, several files changed their
comments to refer to the new location, which isn't strictly necessary
but I did anyway.

The only other change I made was to get rid of the hack I had put in
before, which renamed distcc to distcc-bin.  I had needed to do that
before, temporarily, because "distcc" was already the name of a
directory, and couldn't also be the name of a binary.  Now that the
distcc directory is going away, I can rename the target back to
distcc.

Tested by running './autogen; ./configure; make maintainer-check'.
I also ran 'make pump-check' and 'make distcheck'.

To be reviewed (post-facto) by klarlund@google.com and fergus@google.com

level.  I'm doing this in two stages, because I don't understand svn
enough to be confident to do it in one.  This first stage just copies
all the files from distcc/FOO to FOO.  Now there are two copies of
each file under distcc; the Makefile/etc uses the one in distcc and
ignores the one at the top level.

The next commit will delete everything under distcc, and rewrite the
Makefile/etc to use the top-level versions instead.