Do a relative path ln command instead of an absolute path one. Some people strangely enough have different directory layouts...

llvm-svn: 143302

llvm-svn: 142764

llvm-svn: 142763

llvm-svn: 142647

Modify the script to output the regressions and passes into categories. My Python-fu could use some improving...

llvm-svn: 142643

llvm-svn: 142640

llvm-svn: 142608

the last compiler built for the previous flavour is used for the next,
for example the Debug clang compiler was being used for the initial build
of the Release LLVM.  Flavors should be independent of each other.  This
especially matters if the compiler built for the previous flavour doesn't
actually work!

llvm-svn: 142607

In fact this commit is not intended to change anything unless you
use one of the new command line flags.

llvm-svn: 142577

llvm-svn: 142559

Duncan pointed out that sometimes CC and CXX are used to specify the compiler. Also that the configure script takes care of finding an appropriate compiler if one's not specified.

llvm-svn: 142489

llvm-svn: 142486

llvm-svn: 142482

llvm-svn: 142369

llvm-svn: 142282

llvm-svn: 142280

llvm-svn: 142185

llvm-svn: 142173

This removes support for building llvm-gcc. It will eventually add support for
building other projects.

llvm-svn: 142165

llvm-svn: 142155

llvm-svn: 142098

llvm-svn: 142097

to have structured log files rather than one big file produced by
piping output.

llvm-svn: 128378

I think it was written by Pawel Worach.

llvm-svn: 128268

llvm-svn: 127224

llvm-svn: 127155

llvm-svn: 113965

llvm-svn: 113747

llvm-svn: 113479

llvm-svn: 113401

llvm-svn: 113398

llvm-svn: 113395

llvm-svn: 113393

2-phase build of llvm and llvm-gcc, similar to what the buildbots do, and runs
the regression testsuite.

Things to do:

- Work out some bugs with llvm-gcc flags.
- Not all platforms support ObjC.
- Run the test-suite.

llvm-svn: 113382