I've put the pre-release tar balls here: http://llvm.org/prereleases/1.7/ I'm asking for help to test this release and to review documentation. If anyone can spare some time to help out, I would really appreciate it. The more people that test, the better this release will be. Secondly, now that the tarballs have been created, everyone is free to check in documentation changes into the the release branch (and cvs main too). For code changes, please check them into mainline CVS, then email me to let me know that they should be pulled into the release. For testing, we would like a mix of people to do x86 and ppc. Please send email to the list if you plan to test, what architecture, and if you will use the llvm-gcc binary or compile it yourself. That way, I know who to expect results from. Here are some basic guidelines. 1) Build and install llvmgcc, or use the binary. 2) Build llvm. It would be great if some could do objdir != srcdir and vice versa. You could also try doing a make install. 3) Once everything is ready, run make check (report results) 4) Lastly, run the tests in llvm-test. Report results. I know this may be a bit rushed, but if the testing and documentation review could be completed by April 18th, that would be great. Please either commit updates to the documentation, or mail patches to the llvmbugs list. Future releases will be more organized and provide more time for testing. I know everyone has busy schedules, so I appreciate all the help. Thanks, Tanya
Hi I am doing work on a powerPC based Openbsd 3.8 system iBookg4 and on OpenBSD 3.8 i386. Are these supported in the build system yet. I got 1.6 to build but the gcc-llvm was a no go in configure except by gentle hand building each section and figuring out what it wanted as I went... I notice Support for OpenBSD 2.8 which is quite dated... I am using pro-Police compiler GCC 3.3 but would like to use some of the benifits of llvm on the MacPPC's/i386 on a more modern version of Canadian OpenBSD 3.8 or 3.9 is good too. WHat can I do? Who build your current config script can I talk with them? Where is llvmgcc built from?? I am only interested in C builds, I do not need C++ or java or others. thanks so much for any pointers or help. :) regards, IVO(josephAltea) Tanya Lattner <tonic at nondot.org> wrote: I've put the pre-release tar balls here: http://llvm.org/prereleases/1.7/ I'm asking for help to test this release and to review documentation. If anyone can spare some time to help out, I would really appreciate it. The more people that test, the better this release will be. Secondly, now that the tarballs have been created, everyone is free to check in documentation changes into the the release branch (and cvs main too). For code changes, please check them into mainline CVS, then email me to let me know that they should be pulled into the release. For testing, we would like a mix of people to do x86 and ppc. Please send email to the list if you plan to test, what architecture, and if you will use the llvm-gcc binary or compile it yourself. That way, I know who to expect results from. Here are some basic guidelines. 1) Build and install llvmgcc, or use the binary. 2) Build llvm. It would be great if some could do objdir != srcdir and vice versa. You could also try doing a make install. 3) Once everything is ready, run make check (report results) 4) Lastly, run the tests in llvm-test. Report results. I know this may be a bit rushed, but if the testing and documentation review could be completed by April 18th, that would be great. Please either commit updates to the documentation, or mail patches to the llvmbugs list. Future releases will be more organized and provide more time for testing. I know everyone has busy schedules, so I appreciate all the help. Thanks, Tanya _______________________________________________ LLVM Developers mailing list LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev --------------------------------- 24 FIFA World Cup tickets to be won with Yahoo! Mail. Learn more -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20060416/cc5b52b2/attachment.html>
On Sun, 16 Apr 2006, Tanya Lattner wrote:> For testing, we would like a mix of people to do x86 and ppc. Please send > email to the list if you plan to test, what architecture, and if you will use > the llvm-gcc binary or compile it yourself. That way, I know who to expect > results from.I will test on Darwin/PPC, I'll try the precompiled llvmgcc, objdir != srcdir. -Chris -- http://nondot.org/sabre/ http://llvm.org/
Hi Tanya, Attached are the "make check" results from my machine Darwin Bill-Wendlings-Computer.local 8.6.0 Darwin Kernel Version 8.6.0: Tue Mar 7 16:58:48 PST 2006; root:xnu-792.6.70.obj~1/RELEASE_PPC Power Macintosh powerpc I'll have the llvm-test results available later. -bw -------------- next part -------------- A non-text attachment was scrubbed... Name: check.out Type: application/octet-stream Size: 6548 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20060416/e8c2cefc/attachment.obj>
I would like to test but the I modigied the configure to make unknown = OpenBSD and Unix and go pretty far but it died right after 'supports mkdir' yes... then the next line was 'your system is unsupported'' I have gcc 3.3 on OpenBSD 3.3 pro-police stack compiler... I am only really interested in testing the C/C++ but C primarily for my work. regards, Joseph Altea Chris Lattner <sabre at nondot.org> wrote: On Sun, 16 Apr 2006, Tanya Lattner wrote:> For testing, we would like a mix of people to do x86 and ppc. Please send > email to the list if you plan to test, what architecture, and if you will use > the llvm-gcc binary or compile it yourself. That way, I know who to expect > results from.I will test on Darwin/PPC, I'll try the precompiled llvmgcc, objdir != srcdir. -Chris -- http://nondot.org/sabre/ http://llvm.org/ _______________________________________________ LLVM Developers mailing list LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev --------------------------------- Switch an email account to Yahoo! Mail, you could win FIFA World Cup tickets. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20060417/d54b69db/attachment.html>
Are us on Mac OSX or GNU Darwin without apple OS... I am trying to get it going on OpenBSD 3.8/3.9 latest but seems that the compiler boffs on this system... Should I send the configure output-- could anybody maybe have a hint about why its blowing up...? regards, Joseph Altea Bill Wendling <isanbard at gmail.com> wrote: Hi Tanya, Attached are the "make check" results from my machine Darwin Bill-Wendlings-Computer.local 8.6.0 Darwin Kernel Version 8.6.0: Tue Mar 7 16:58:48 PST 2006; root:xnu-792.6.70.obj~1/RELEASE_PPC Power Macintosh powerpc I'll have the llvm-test results available later. -bw _______________________________________________ LLVM Developers mailing list LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev --------------------------------- 24 FIFA World Cup tickets to be won with Yahoo! Mail. Learn more -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20060417/014adfa3/attachment.html>
I'll test on Darwin/PPC, precompiled llvmgcc, objdir == srcdir. Rob On Apr 16, 2006, at 1:42 PM, Chris Lattner wrote:> On Sun, 16 Apr 2006, Tanya Lattner wrote: >> For testing, we would like a mix of people to do x86 and ppc. >> Please send email to the list if you plan to test, what >> architecture, and if you will use the llvm-gcc binary or compile >> it yourself. That way, I know who to expect results from. > > I will test on Darwin/PPC, I'll try the precompiled llvmgcc, > objdir != srcdir. > > -Chris > > -- > http://nondot.org/sabre/ > http://llvm.org/ > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdevRobert L. Bocchino Jr. Ph.D. Student, Computer Science University of Illinois, Urbana-Champaign -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20060418/dde8b895/attachment.html>
On 4/16/06, Tanya Lattner <tonic at nondot.org> wrote:> > I've put the pre-release tar balls here: > http://llvm.org/prereleases/1.7/ >The build failed on i686-pc-linux-gnu. llvm[2]: Flexing FileLexer.l llvm[2]: Compiling FileLexer.cpp for Release build /home/rogelio/Desktop/llvm/utils/TableGen/FileLexer.l: In function 'int Filelex()': /home/rogelio/Desktop/llvm/utils/TableGen/FileLexer.l:205: error: 'STRCONCATTOK' was not declared in this scope Lexer.cpp: In function 'int yy_get_next_buffer()': Lexer.cpp:1369: warning: comparison between signed and unsigned integer expressions make[2]: *** [/home/rogelio/Desktop/llvm/utils/TableGen/Release/FileLexer.o] Error 1 make[2]: Leaving directory `/home/rogelio/Desktop/llvm/utils/TableGen' make[1]: *** [all] Error 1 make[1]: Leaving directory `/home/rogelio/Desktop/llvm/utils' make: *** [all] Error 1 any suggestions how to debug this? Krgds, Roger
On 4/19/06, Rogelio Serrano <rogelio.serrano at gmail.com> wrote:> On 4/16/06, Tanya Lattner <tonic at nondot.org> wrote: > > > > I've put the pre-release tar balls here: > > http://llvm.org/prereleases/1.7/ > > > > The build failed on i686-pc-linux-gnu. > > llvm[2]: Flexing FileLexer.l > llvm[2]: Compiling FileLexer.cpp for Release build > /home/rogelio/Desktop/llvm/utils/TableGen/FileLexer.l: In function > 'int Filelex()': > /home/rogelio/Desktop/llvm/utils/TableGen/FileLexer.l:205: error: > 'STRCONCATTOK' was not declared in this scope > Lexer.cpp: In function 'int yy_get_next_buffer()': > Lexer.cpp:1369: warning: comparison between signed and unsigned > integer expressions > make[2]: *** [/home/rogelio/Desktop/llvm/utils/TableGen/Release/FileLexer.o] > Error 1 > make[2]: Leaving directory `/home/rogelio/Desktop/llvm/utils/TableGen' > make[1]: *** [all] Error 1 > make[1]: Leaving directory `/home/rogelio/Desktop/llvm/utils' > make: *** [all] Error 1 > > any suggestions how to debug this? > > Krgds, > Roger >Ialready figured it out. I ran the build in the source dir. -- www.smsglobal.net SMS Global Ltd Short Message Service For Seafarers
This came up when trying to compile the Python bindings against llvm 1.7. File include/llvm/Transforms/Scalar.h declares llvm::createPREPass(), which does not seem to be implemented anywhere. Should I report this in llvmbugs? -- Pertti
Hi Pertti, The boost Python are not (yet) part of LLVM so I suppose it would make most sense to try to makes fixes/changes so they would work for 1.7 and then try to get them into LLVM CVS. It would be good in such a case to ask the author of the bindings again if he would allow this, because basicaly I think he has to agree to the LLVM lincense. cheers, Eric On Apr 20, 2006, at 5:08 PM, Pertti Kellomäki wrote:> This came up when trying to compile the Python bindings > against llvm 1.7. File include/llvm/Transforms/Scalar.h > declares llvm::createPREPass(), which does not seem to > be implemented anywhere. Should I report this in llvmbugs? > -- > Pertti > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
Pertti Kellomäki wrote:> This came up when trying to compile the Python bindings > against llvm 1.7. File include/llvm/Transforms/Scalar.h > declares llvm::createPREPass(), which does not seem to > be implemented anywhere. Should I report this in llvmbugs?Just to clarify myself: this is an issue with the LLVM sources, not with the Python bindings. -- Pertti
Reasonably Related Threads
- [LLVMdev] OpenBSD. (Was: 1.7 Pre-Release Ready for Testing)
- [LLVMdev] 1.7 Pre-Release Ready for Testing
- [LLVMdev] OpenBSD. (Was: 1.7 Pre-Release Ready for Testing)
- [LLVMdev] OpenBSD. (Was: 1.7 Pre-Release Ready for Testing)
- [LLVMdev] 1.7 Pre-Release Ready for Testing