search for: cppljevans

We had to roll a release candidate 4 for the 3.5 release. It’s up at the normal place: http://llvm.org/pre-releases/3.5 Please test it and report any major bugs you may find. Thanks! -bw

On Sun, Dec 30, 2012 at 1:58 AM, Larry Evans <cppljevans at suddenlink.net>wrote: > On 12/29/12 18:40, NAKAMURA Takumi wrote: > > 2012/12/30 Larry Evans <cppljevans at suddenlink.net>: > >> I just created clang with the tarballs without problem; however, > >> when `make check-all` was run, I got 1 error. My system is...

On 12/06/12 01:12, Pawel Wodnicki wrote: > Hello, > > Release Candidate 3 has been branched. > RC3 source code can be downloaded as tarballs from: > > http://llvm.org/pre-releases/3.2/rc3/ > > or directly from svn. > > Binaries will be posted shortly. > > Testing > > RC3 has a number of fixes related to MIPS support > that need to be well

2012/12/30 Larry Evans <cppljevans at suddenlink.net>: > I just created clang with the tarballs without problem; however, > when `make check-all` was run, I got 1 error. My system is: > ~/download/llvm/pre-releases/3.2/rc3/download/build_debug $ make check-all > llvm[0]: Running test suite > make[1]: Entering dir...

Hello, Release Candidate 3 has been branched. RC3 source code can be downloaded as tarballs from: http://llvm.org/pre-releases/3.2/rc3/ or directly from svn. Binaries will be posted shortly. Testing RC3 has a number of fixes related to MIPS support that need to be well exercised. Otherwise, I think we are at the point of the release where I can *challenge* testers to try to break it!

On 07/30/2014 10:06 AM, Larry Evans wrote: > On 07/30/2014 12:35 AM, Ben Pope wrote: >> On Wednesday, July 30, 2014 01:31 PM, Ben Pope wrote: >> >>> ldd your_built_clang | grep libstdc++ >>> chrpath -l your_built_clang >> >> Hmm, where "your_built_clang" should be the actual failing executable: >>