Reid, Okay seem to be most of the way there, just a couple of warnings/errors and more failed 'make checks' than before. make check results :- # of expected passes 1735 # of unexpected failures 45 # of expected failures 56 See attached file for details. There were two "errors" flagged up in the LLVM second phase build :- ******** Warning: Your LLVMGCCDIR is set incorrectly. Double-check ******** Warning: llvm/Makefile.config to make sure it matches ******** Warning: the directory where the C front-end is installed, ******** Warning: and re-run configure if it does not. /usr/src/llvm/Makefile.rules:639: Modules require llvm-gcc but no llvm-gcc is av ailable **** Although as far as I can tell they had no effect and 'llvm-gcc.exe' was accessable on the path to both the make and make install runs where they occured. Other than that, we are winning. Aaron -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20050602/82f7c107/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/82f7c107/attachment.txt>
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. 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? 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. Reid. On Thu, 2005-06-02 at 21:37 +0100, Aaron Gray wrote:> Reid, > > Okay seem to be most of the way there, just a couple of > warnings/errors and more failed 'make checks' than before. > > make check results :- > > # of expected passes 1735 > # of unexpected failures 45 > # of expected failures 56 > > See attached file for details. > > > There were two "errors" flagged up in the LLVM second phase build :- > > ******** Warning: Your LLVMGCCDIR is set incorrectly. Double-check > ******** Warning: llvm/Makefile.config to make sure it matches > ******** Warning: the directory where the C front-end is installed, > ******** Warning: and re-run configure if it does not. > > /usr/src/llvm/Makefile.rules:639: Modules require llvm-gcc but no > llvm-gcc is av > ailable **** > > Although as far as I can tell they had no effect and 'llvm-gcc.exe' > was accessable on the path to both the make and make install runs > where they occured. > > Other than that, we are winning. > > 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/1613e685/attachment.sig>
>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