following improvements:
- Arch/OS/platform-specific files are now included/excluded via the
preprocessor, rather than via the build system. This is more consistent
(we use the pre-processor for small arch/OS/platform-specific chunks
within files) and makes the build system much simpler, as the sources for
all programs are the same on all platforms.
- Vast amounts of cut+paste Makefile.am code has been factored out. If a
new platform is implemented, you need to add 11 extra Makefile.am lines.
Previously it was over 100 lines.
- Vex has been autotoolised. Dependency checking now works in Vex (no more
incomplete builds). Parallel builds now also work. --with-vex no longer
works; it's little use and a pain to support. VEX/Makefile is still in
the Vex repository and gets overwritten at configure-time; it should
probably be renamed Makefile-gcc to avoid possible problems, such as
accidentally committing a generated Makefile. There's a bunch of hacky
copying to deal with the fact that autotools don't handle same-named files
in different directories. Julian plans to rename the files to avoid this
problem.
- Various small Makefile.am things have been made more standard automake
style, eg. the use of pkginclude/pkglib prefixes instead of rolling our
own.
- The existing five top-level Makefile.am include files have been
consolidated into three.
- Most Makefile.am files now are structured more clearly, with comment
headers separating sections, declarations relating to the same things next
to each other, better spacing and layout, etc.
- Removed the unused exp-ptrcheck/tests/x86 directory.
- Renamed some XML files.
- Factored out some duplicated dSYM handling code.
- Split auxprogs/ into auxprogs/ and mpi/, which allowed the resulting
Makefile.am files to be much more standard.
- Cleaned up m_coredump by merging a bunch of files that had been
overzealously separated.
The net result is 630 fewer lines of Makefile.am code, or 897 if you exclude
the added Makefile.vex.am, or 997 once the hacky file copying for Vex is
removed. And the build system is much simpler.
git-svn-id: svn://svn.valgrind.org/valgrind/trunk@10364
- Put the old tree in valgrind-old/ and the new one in valgrind-new/,
instead of using valgrind/ for both. That way, the old tree is still
present after running the tests, so it can be inspected for problems.
This required changing how ABT_RUN_REGTEST worked -- it no longer should
change directories itself -- but I think Bart's machine is the only one
using that and I updated the .conf file accordingly.
- Change some variable names -- only use the "ABT_" prefix for variables
defined in the .conf files, and use $DIR and $TAG to match the README.txt.
git-svn-id: svn://svn.valgrind.org/valgrind/trunk@10248
- Install in $DIR/valgrind/Inst/ rather than $DIR/Inst. Just a bit neater.
- Run "make regtest" instead of "perl tests/vg_regtest --all", because we
might not want to run all tests (eg. we don't on Darwin at the moment).
git-svn-id: svn://svn.valgrind.org/valgrind/trunk@10236
line if the results are unchanged from 24 hours ago. Makes it easier to see
(or filter) if results are unchanged.
git-svn-id: svn://svn.valgrind.org/valgrind/trunk@9334
Use '.' instead of 'source', because that's how /bin/sh does it. This
should make the script more reliable on systems that don't have bash as
the /bin/sh, eg. Ubuntu and Debian.
git-svn-id: svn://svn.valgrind.org/valgrind/trunk@8920
- Check that it is passed two arguments, abort if not (avoids some
possibly confusing behaviour).
- Remove various uses of $ABT_TOP in paths; it's not necessary because
the first thing the script does is 'cd' to $ABT_TOP. Furthemore, some
paths lacked the $ABT_TOP which was confusing.
- Gather up all the diffs from the tests, grab the first 100 lines (or
less, if shorter) of each, and concatenate into a file, the name of
which is passed to the <tag>.sendmail script so it can be attached.
Index: nightly/README.txt
Explain the new 3rd argument.
git-svn-id: svn://svn.valgrind.org/valgrind/trunk@8915
Use '=' instead of '==', which is a bash-ism that doesn't work on
Debian/Ubuntu systems that have dash installed as /bin/sh. It only
mildly affected the script's running -- it made it say that certain
stages failed when really they didn't.
git-svn-id: svn://svn.valgrind.org/valgrind/trunk@8914
trunk/nightly/bin/nightly
trunk/nightly/README.txt
Greatly improved the description of how to use this script; a user now
has a fighting chance of using the script without actually reading it.
trunk/nightly/conf/nemesis.sendmail
trunk/nightly/conf/georgia-tech-cellbuzz.sendmail
Clarified the usage comments.
git-svn-id: svn://svn.valgrind.org/valgrind/trunk@8913
- Added support for the variable ABT_RUN_REGTEST, the command to run the regression tests.
- Added support for the variable ABT_CONFIGURE_OPTIONS, such that extra command line options
can be passed to the configure script.
- Cross-compilation patch is applied after source code checkout and before the source code is
compiled.
git-svn-id: svn://svn.valgrind.org/valgrind/trunk@8588
regtest" and "make exp-regtest". Then change the nightly build system
to run all-regtest instead of exp-regtest.
git-svn-id: svn://svn.valgrind.org/valgrind/trunk@7332
the last 24 hours. This saves you from having to scroll down to
determine this when the number of failures is large (eg on PPC).
git-svn-id: svn://svn.valgrind.org/valgrind/trunk@4431
don't put a dependency between the install target and $(BUILT_SOURCES)
so doing a straight install doesn't work.
git-svn-id: svn://svn.valgrind.org/valgrind/trunk@3494
steps fails instead of carrying on with the other steps - this should
help ensure that the log fragment sent out contains useful information.
A second change is to ensure that if the regression tests complete
then the full results are included in the email - if they don't
complete then just the last 20 lines of output are sent as before.
git-svn-id: svn://svn.valgrind.org/valgrind/trunk@3491
