(C Tests) Including <linux/types.h> is not portable

Applications should never include anything from /usr/include/linux if
they expect to be portable across multiple versions of Linux.

The C99 fixed-length integer types are defined in <inttypes.h> and
<stdint.h>, so one of them should be included.

The "u_char" type is not a standard type and using these ugly types
is not portable because there's no way to tell whether we need to
define the type ourselves, and defining it ourself when it is already
defined is an error.  I've replaced "u_char" with "unsigned char".
(C++ Tests) Any test specimen that includes boost headers must have boost include directories

The extractFunctionArgumentsTests assumed that boost header files are located in a well
known directory, but this isn't always the case.  I've changed the test to use the same
boost header directory as used by librose itself (although no attempt to add it earliest
in the search path, so the headers in /usr/include might still get used instead of the
boost headers used by librose).
(C++ Tests) Commented out a broken test

The test2013_242.C fails the normalizationTranslator test because it
can't be parsed by ROSE when using boost 1.47. Since this failure is
unrelated to the normalizationTranslator test itself, I have disabled
the test for this single specimen.

In buildTemplateClassDeclaration_nfi(): detected isSgClassType(nondefdecl->get_type())->get_declaration() != isSgDeclarationStatement(nondefdecl) (problem with Boost code in ROSE compiling ROSE)
(C++ Tests) Fixed boost include dir; commented out broken test

* Any test specimen that includes boost headers must have boost
  include directories. The singleStatementToBlockNormalization
  makefile assumed that boost header files are located in a well known
  directory, but this isn't always the case.  I've changed the test to
  use the same boost header directory as used by librose itself
  (although no attempt to add it earliest in the search path, so the
  headers in /usr/include might still get used instead of the boost
  headers used by librose).

* The test2013_242.C fails the singleStatementToBlockNormalization
  test because it can't be parsed by ROSE when using boost 1.47 with
  debugging enabled. Since this failure is unrelated to the
  normalizationTranslator test itself, I have disabled the test for
  this single specimen.
(Testing) Fixed programAnalysis/sideEffectAnalysisTests

* Fixed the makefile so the tests can be run in parallel

* Fixed the test answers because column numbers were wrong for
  function calls.  In a call like "<expression>(<args>)", ROSE
  at one time used the beginning of the expression as the column
  for the SgFunctionCallExp node, and now it uses the left paren.

* Fixed the order of arguments to "diff" to be consistent with
  the other tests.  The output should show how the expected
  answer must be changed to match the actual result, but it
  was vice versa.

* Change names of answers.  If the input is "foo.C" then the
  answer is named "foo.C.ans" rather than "foo.outx". This is
  consistent with other makefiles that compare output against
  a known good answer.
(Build) Switched config to use Java 7
(Testing) Rewrote a very messy makefile while trying to debug what passes

The various lists of test specimens were confusing because it wasn't clear
which lists were actually used and whether commenting out a list meant that
the test for those specimens fail, pass, or are not run.

The new makefile runs the exact same tests for "make check" as the old
makefile, with the exception that test2013_242.C is now marked as a failing
test and not run.  This specimen fails with an error "(problem with Boost
code in ROSE compiling ROSE)" and the assertion "current_scope->lookup_symbol(
aliasedName,__null,__null) != __null" failed. This is on Debian Squeeze
using x86_64-linux-gnu g++ 4.4.5-8 and boost 1.47.
(Testing) Ability to change timeout inside makefile for $(RTH_RUN)

When using $(srcdir)/scripts/test_exit_status as the config file,
you can add TIMEOUT=X to the $(RTH_RUN) command to override the
default timeout, which is 15 minutes ("15m").
(Testing) Documentation; only comments changed
(Testing) Increased timeout for a few tests from 15m to 45m

I'm not sure why these tests take so long, but even on a 3.33GH
machine with 12 cores and 48GB memory they take nearly 40 minutes
if ROSE is compiled with full debugging.
(Testing) Makefile cleaned up and rewritten to use $(RTH_RUN)
Merge remote branch 'rc/master' into support
Merge remote branch 'rc/master' into support

Conflicts:
	tests/CompileTests/Cxx_tests/Makefile.am
		Mostly reverted to remote changes because there
		were too many conflicts and my local changes
		were quite old.
	tests/roseTests/programTransformationTests/extractFunctionArgumentsTest/Makefile.am
Merge remote branch 'rc/master' into debian
(C tests) Including <linux/*> is not recommended

Commented out <linux/types.h> since uint32_t should be
available in user-space headers on Rhel5.  Trying <stdint.h>.

https://lwn.net/Articles/113349/