-% cd llvm/projects +% cd ~/llvm/projects % svn co http://llvm.org/svn/llvm-project/test-suite/trunk test-suite % cd .. -% ./configure --with-llvmgccdir=$LLVM_GCC_DIR
where $LLVM_GCC_DIR is the directory where -you installed llvm-gcc, not its src or obj -dir. The --with-llvmgccdir option assumes that -the llvm-gcc-4.2 module was configured with ---program-prefix=llvm-, and therefore that the C and C++ -compiler drivers are called llvm-gcc and llvm-g++ -respectively. If this is not the case, -use --with-llvmgcc/--with-llvmgxx to specify each -executable's location.
+and then configure and build normally as you would from the +Getting Started +Guide. This will autodetect first the built clang if you are building +clang, then clang in your path and finally look for llvm-gcc +in your path.
Then, run the entire test suite by running make in the test-suite -directory:
+subdirectory of your build directory:-% cd projects/test-suite +% cd where-you-built-llvm/projects/test-suite % gmake
Usually, running the "nightly" set of tests is a good idea, and you can also +
Usually, running the "simple" set of tests is a good idea, and you can also let it generate a report by running:
-% cd projects/test-suite -% gmake TEST=nightly report report.html +% cd where-you-built-llvm/projects/test-suite +% gmake TEST=simple report report.html