Dale Johannesen wrote:> On Feb 6, 2009, at 8:52 PM, Patrick Simmons wrote: > > >> Hi, >> >> I'm trying to run the tests in llvm-suite, but I've run into trouble. >> First, I had the llvm-suite checkout in a directory alongside the llvm >> compiler checkout, but, when I ran "make" from llvm-suite, it >> complained >> about there not being a Makefile two levels above it, so I moved >> llvm-suite into the "test" subdirectory inside the llvm compiler >> checkout. I ran "make" again, but I got this: >> > > You need to put it under the "projects" subdirectory. Read this: > http://llvm.org/docs/TestingGuide.html > > It is perhaps a little confusing; looks like you stopped reading after > the first "test suite" section. Keep going. > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >Thanks, Dale. I did what you said, and I can run the test suite now. Unfortunately, the tests all fail, with cc1 complaining about unknown debugging options being passed to it. The two possible causes I can think of for this are that I passed "--enable-optimized" when configuring LLVM, and that I used the GCC frontend located in /home/vadve/shared/llvm-gcc-4.2 instead of compiling the GCC frontend myself (I added the bin directory to my PATH). Do you think either of these things could be responsible? Thanks again, --Patrick -- If I'm not here, I've gone out to find myself. If I get back before I return, please keep me here.
Patrick Simmons wrote:> Dale Johannesen wrote: >> On Feb 6, 2009, at 8:52 PM, Patrick Simmons wrote: >> >> >>> Hi, >>> >>> I'm trying to run the tests in llvm-suite, but I've run into trouble. >>> First, I had the llvm-suite checkout in a directory alongside the llvm >>> compiler checkout, but, when I ran "make" from llvm-suite, it >>> complained >>> about there not being a Makefile two levels above it, so I moved >>> llvm-suite into the "test" subdirectory inside the llvm compiler >>> checkout. I ran "make" again, but I got this: >>> >> >> You need to put it under the "projects" subdirectory. Read this: >> http://llvm.org/docs/TestingGuide.html >> >> It is perhaps a little confusing; looks like you stopped reading >> after the first "test suite" section. Keep going. >> >> _______________________________________________ >> LLVM Developers mailing list >> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu >> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >> > Thanks, Dale. I did what you said, and I can run the test suite now. > Unfortunately, the tests all fail, with cc1 complaining about unknown > debugging options being passed to it. The two possible causes I can > think of for this are that I passed "--enable-optimized" when > configuring LLVM, and that I used the GCC frontend located in > /home/vadve/shared/llvm-gcc-4.2 instead of compiling the GCC frontend > myself (I added the bin directory to my PATH). Do you think either of > these things could be responsible? > > Thanks again, > --Patrick >That should be /home/vadve/shared/llvm-gcc4.2, sorry for the typo. It was correct in my PATH. --Patrick -- If I'm not here, I've gone out to find myself. If I get back before I return, please keep me here.
On Feb 8, 2009, at 11:23 AMPST, Patrick Simmons wrote:>>> >>> You need to put it under the "projects" subdirectory. Read this: >>> http://llvm.org/docs/TestingGuide.html >>> >>> It is perhaps a little confusing; looks like you stopped reading >>> after the first "test suite" section. Keep going. >>> >>> _______________________________________________ >>> LLVM Developers mailing list >>> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu >>> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >>> >> Thanks, Dale. I did what you said, and I can run the test suite now. >> Unfortunately, the tests all fail, with cc1 complaining about unknown >> debugging options being passed to it. The two possible causes I can >> think of for this are that I passed "--enable-optimized" when >> configuring LLVM, and that I used the GCC frontend located in >> /home/vadve/shared/llvm-gcc-4.2 instead of compiling the GCC frontend >> myself (I added the bin directory to my PATH). Do you think either >> of >> these things could be responsible? >> >> Thanks again, >> --Patrick >> > That should be /home/vadve/shared/llvm-gcc4.2, sorry for the typo. It > was correct in my PATH.I've never used that FE, I've always built my own. So it seems possible that's the problem. I don't personally use -enable-optimized much, but other people do; that seems unlikely.