similar to: [LLVMdev] Buildbots: Apology and Explanation

On Aug 30, 2009, at 10:18 AM, Paul Melis wrote: > Hello, > > Bill Wendling wrote: >> Before we had buildbots, a random patch would break the system. It >> would sometimes take a whole day to determine which patch broke it. > I see the buildbots are currently showing no problem on 32-bit linux > but > I get the following build error with TOT (out-of-source autoconf

On Aug 31, 2009, at 6:48 AM, Paul Melis wrote: > Paul Melis wrote: >> Jim Grosbach wrote: >>> >>> On Aug 30, 2009, at 10:18 AM, Paul Melis wrote: >>> >>>> Hello, >>>> >>>> Bill Wendling wrote: >>>>> Before we had buildbots, a random patch would break the system. It >>>>> would sometimes take a

Hello, Bill Wendling wrote: > Before we had buildbots, a random patch would break the system. It > would sometimes take a whole day to determine which patch broke it. I see the buildbots are currently showing no problem on 32-bit linux but I get the following build error with TOT (out-of-source autoconf build): [...] make[1]: Leaving directory `/home/melis/c/llvm-svn-release/tools'

Paul Melis wrote: > Jim Grosbach wrote: >> >> On Aug 30, 2009, at 10:18 AM, Paul Melis wrote: >> >>> Hello, >>> >>> Bill Wendling wrote: >>>> Before we had buildbots, a random patch would break the system. It >>>> would sometimes take a whole day to determine which patch broke it. >>> I see the buildbots are currently

Jim Grosbach wrote: > > On Aug 30, 2009, at 10:18 AM, Paul Melis wrote: > >> Hello, >> >> Bill Wendling wrote: >>> Before we had buildbots, a random patch would break the system. It >>> would sometimes take a whole day to determine which patch broke it. >> I see the buildbots are currently showing no problem on 32-bit linux >> but >> I

Paul Melis wrote: > Paul Melis wrote: > >> Jim Grosbach wrote: >> >>> On Aug 30, 2009, at 10:18 AM, Paul Melis wrote: >>> >>> >>>> Hello, >>>> >>>> Bill Wendling wrote: >>>> >>>>> Before we had buildbots, a random patch would break the system. It >>>>>

Hi Bill, > ... Still, people would break the builds and let > things go for hours or days at a time. don't forget the time-zone effect. I regularly get build failures in the morning, presumably because someone in the US committed just before going to bed. I guess they are happily snoring away when the build-bots (and humans) start complaining! So when hours go by without a fix, it

On Oct 20, 2009, at 12:05 PM, Aaron Gray wrote: > 2009/10/20 Tanya Lattner <lattner at apple.com>: >> >> On Oct 20, 2009, at 5:49 AM, Jay Foad wrote: >> >>>> To test clang: >>>> 1) Compile llvm and clang from source. >>> >>> LLVM fails to build for me on Cygwin. I get: >>> >> >> Does TOT build? If not,

2009/10/20 Tanya Lattner <lattner at apple.com>: > > On Oct 20, 2009, at 12:05 PM, Aaron Gray wrote: > >> 2009/10/20 Tanya Lattner <lattner at apple.com>: >>> >>> On Oct 20, 2009, at 5:49 AM, Jay Foad wrote: >>> >>>>> To test clang: >>>>> 1) Compile llvm and clang from source. >>>> >>>> LLVM

On Sat, Aug 29, 2009 at 4:15 AM, Duncan Sands<baldrick at free.fr> wrote: > Hi Bill, > >> ... Still, people would break the builds and let >> things go for hours or days at a time. > > don't forget the time-zone effect.  I regularly get build > failures in the morning, presumably because someone in the > US committed just before going to bed.  I guess they

On Oct 20, 2009, at 5:49 AM, Jay Foad wrote: >> To test clang: >> 1) Compile llvm and clang from source. > > LLVM fails to build for me on Cygwin. I get: > Does TOT build? If not, please file a bug. Unfortunately Cygwin is not in our release criteria. I'd like to have a buildbot running (if there is not one already) and then get someone to qualify it for the

On Sat, Aug 29, 2009 at 9:44 AM, Kenneth Uildriks<kennethuil at gmail.com> wrote: > On Sat, Aug 29, 2009 at 4:15 AM, Duncan Sands<baldrick at free.fr> wrote: >> Hi Bill, >> >>> ... Still, people would break the builds and let >>> things go for hours or days at a time. >> >> don't forget the time-zone effect.  I regularly get build

> To test clang: > 1) Compile llvm and clang from source. LLVM fails to build for me on Cygwin. I get: make[1]: Entering directory `/home/foad/llvm/objdir-2.6/runtime' make[2]: Entering directory `/home/foad/llvm/objdir-2.6/runtime/libprofile' llvm[2]: Compiling BasicBlockTracing.c for Release build (PIC) llvm[2]: Compiling BlockProfiling.c for Release build (PIC) llvm[2]:

2009/10/20 Tanya Lattner <lattner at apple.com>: > > On Oct 20, 2009, at 5:49 AM, Jay Foad wrote: > >>> To test clang: >>> 1) Compile llvm and clang from source. >> >> LLVM fails to build for me on Cygwin. I get: >> > > Does TOT build? If not, please file a bug. No. Theres the runtime install bug (below), and llvm-gcc has a bug that I

I am getting the following on 'make install' on Cygwin both on debug and release builds :- llvm[3]: Installing Release /home/ang/llvm-coff/bin/llvmc.exe make[3]: Leaving directory `/home/ang/build/llvm-coff/tools/llvmc/driver' make[2]: Leaving directory `/home/ang/build/llvm-coff/tools/llvmc' make[1]: Leaving directory `/home/ang/build/llvm-coff/tools' make[1]: Entering

Hi, when I try to build libprofile with r80670 (both llvm and llvm-gcc) I get this error: make[1]: Entering directory `.../llvm-svn-debug-obj/runtime/libprofile' llvm[1]: Building Debug Bytecode Archive libprofile_rt.bca (internalize) llvm[1]: Installing Debug Shared Library /nfs/a5/astifter/astifter/llvm/llvm-svn-debug-obj/../llvm-svn-debug-install/lib/libprofile_rt.so 0 llvm-ld

LLVMers, 2.6 pre-release2 is ready to be tested by the community. http://llvm.org/prereleases/2.6/ If you have time, I'd appreciate anyone who can help test the release. To test llvm-gcc: 1) Compile llvm from source and untar the llvm-test in the projects directory (name it llvm-test or test-suite). Choose to use a pre- compiled llvm-gcc or re-compile it yourself. 2) Run make check,

Hi, Thanks for the replies in the mailing list. I made some progress in building LLVM, but I still have a problem about ELF class. I am working with LLVM on a sparcv9 machine, while the gcc is configured to emit 32-bit binary by default. After executing "configure --with-llvmgccdir=... --enable-jit", I modified Makefile.config so it contains CXX = g++ -mcpu=v9 -m64 CC := gcc -mcpu=v9

Hi Nick Thanks for you reply. CMAKE is very new to me. I complied using GNU WIN32 and got those errors. Is it possible to compile it using GNU WIN 32 and anything need to be modified? I managed to compile the run time library on a mac machine. Yafan On Fri, Apr 22, 2011 at 5:04 PM, Nick Lewycky <nicholas at mxc.ca> wrote: > yafan zhao wrote: > >> Hi All >> Thanks for

As you all have undoubtedly noticed, I recently did Yet Another Merge to Apple's GCC top-of-tree. This merge was prompted by several important fixes in the "blocks" implementation. There are still many testcases that need to be moved over, but those can come at our leisure. I compiled both the "Apple way" and the "FSF way". It also passed the tests in