>>> Looks like it couldn't find llvm-gcc. >> >> Its on the path. > > Is it set in site.exp?Thats it, great. Should I be testing the 2.0 candiate release from CVS or are you releasing .tar.gz's ? Thanks alot, Aaron
>> Is it set in site.exp? > > Thats it, great. > > Should I be testing the 2.0 candiate release from CVS or are you releasing > .tar.gz's ?I'll be sending out more instructions tonight, but I'll be sending out tarballs but people can test from the branch too. I need to do some more merging into the branch tonight. -Tanya
On Tue, 2007-05-08 at 20:36 +0100, Aaron Gray wrote:> >>> Looks like it couldn't find llvm-gcc. > >> > >> Its on the path. > > > > Is it set in site.exp? > > Thats it, great.Aaron, Please note that the path is (purposefully) not used to locate test executables. Many of us have many LLVM environments and using the path leads to confusion. What the makefile is looking for is the LLVMGCC variable to be set. It wasn't so when substituted you get a null string which leads to attempting to execute "-emit-llvm" (the first argument after the null program name). You can resolve this by using the --with-llvmgccdir option when configuring llvm. Reid.> > Should I be testing the 2.0 candiate release from CVS or are you releasing > .tar.gz's ? > > Thanks alot, > > Aaron > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
> Please note that the path is (purposefully) not used to locate test > executables. Many of us have many LLVM environments and using the path > leads to confusion. What the makefile is looking for is the LLVMGCC > variable to be set. It wasn't so when substituted you get a null string > which leads to attempting to execute "-emit-llvm" (the first argument > after the null program name). You can resolve this by using the > --with-llvmgccdir option when configuring llvm.Right I will amend my proceedure. Its odd as it has worked fine uptil now. Thanks, Aaron
Hi Reid,> Please note that the path is (purposefully) not used to locate test > executables. Many of us have many LLVM environments and using the path > leads to confusion. What the makefile is looking for is the LLVMGCC > variable to be set. It wasn't so when substituted you get a null > string which leads to attempting to execute "-emit-llvm" (the first > argument after the null program name). You can resolve this by using > the --with-llvmgccdir option when configuring llvm.Might the makefile have an early target that does the shell if test x$LLVMGCC = x; then echo error message >&2; exit 1; fi in order to trap this common problem. Cheers, Ralph.