>Your "make check" output has two classes of errors:>1. llvm-gcc or llvm-g++ not being found. Its possible this results from >Cygwin requiring the .exe extension. The makefiles probably need to be >enhanced to include the suffix.Okay, but that did not seem to be a problem before. I thought about that being a possible problem. The make install removes the .exe extensions. But it does stop them being executed outside of Cygwin/bash.>2. You have a permissions problem on: >test/Regression/Analysis/Andersens/Output/basictest.ll.out.script. The >file couldn't be opened for writing. Possibly you have a hung build or >the permissions are just plain wrong?No .script file there there is basictest.ll.out however.>The messages indicating that LLVMGCCDIR is not set properly probably >also originate from not having the .exe suffix placed correctly. I'll >see if I can work up a patch for you.Okay. Shall I do the ENABLE_OPTIMIZED "release" build now or wait till we have ironed out these last few problems; and do it tommorow. You have not commited the X86JITInfo.cpp patch yet ? Thanks again for the support, hopefully we will get it solved soon. Aaron
On Thu, 2005-06-02 at 22:21 +0100, Aaron Gray wrote:> >Your "make check" output has two classes of errors: > > >1. llvm-gcc or llvm-g++ not being found. Its possible this results from > >Cygwin requiring the .exe extension. The makefiles probably need to be > >enhanced to include the suffix. > > Okay, but that did not seem to be a problem before.Well, it is now :) I'm working on fixing the configure script. It doesn't include the .exe suffix which is why you're getting these errors.> I thought about that being a possible problem. The make install removes the > .exe extensions. > But it does stop them being executed outside of Cygwin/bash. > > >2. You have a permissions problem on: > >test/Regression/Analysis/Andersens/Output/basictest.ll.out.script. The > >file couldn't be opened for writing. Possibly you have a hung build or > >the permissions are just plain wrong? > > No .script file there there is basictest.ll.out however.Then the permission problem is on the Output directory. The file can't be created for some strange reason.> >The messages indicating that LLVMGCCDIR is not set properly probably > >also originate from not having the .exe suffix placed correctly. I'll > >see if I can work up a patch for you. > > Okay. > > Shall I do the ENABLE_OPTIMIZED "release" build now or wait till we have > ironed out these last few problems; and do it tommorow.You'll run into the same problem with that style build. Go ahead and kick it off if you like, at least you'll get the bulk of the compilation over and done with.> > You have not commited the X86JITInfo.cpp patch yet ?No, I've been waiting for confirmation that it solved the problem, but I guess we have that now that you've moved passed that issue.> > Thanks again for the support, hopefully we will get it solved soon.Yes, hopefully! Reid -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20050602/93e15412/attachment.sig>
Reid, Heres the results, even better than before :- # of expected passes 1759 # of unexpected failures 12 # of expected failures 56 Previous working build :- # of expected passes 1736 # of unexpected failures 16 # of expected failures 56 Goodie, now for a release build. Aaron -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20050602/882c1034/attachment.html> -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: makecheck.txt URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20050602/882c1034/attachment.txt>
Okay, this is looking much better. I'll commit the configure script. There's a couple of CFrontEnd failures. Possibly you're not working with the latest llvm-gcc? (built from CVS?) The others are known JIT failures on Cygwin .. it can't load symbols from the LLI executable. We don't have a fix for this (yet). So, I'd say we're good to go :) Reid. On Thu, 2005-06-02 at 23:21 +0100, Aaron Gray wrote:> Reid, > > Heres the results, even better than before :- > > # of expected passes 1759 > # of unexpected failures 12 > # of expected failures 56 > > Previous working build :- > > # of expected passes 1736 > # of unexpected failures 16 > # of expected failures 56 > > Goodie, now for a release build. > > Aaron > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://mail.cs.uiuc.edu/mailman/listinfo/llvmdev-------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20050602/533970c7/attachment.sig>