On Tue, Jul 20, 2010 at 8:25 AM, Marcelo/Porks wrote:
> On Wed, Jul 14, 2010 at 3:38 PM, Roman Divacky wrote:
>> hi,
>>
>> ClangBSD was updated to LLVM/clang revision r108243 which we plan to
>> merge into HEAD. We would like that revision to be tested as much as possible
>> and therefore we ask
On Wed, Jul 14, 2010 at 3:38 PM, Roman Divacky wrote:
> hi,
>
> ClangBSD was updated to LLVM/clang revision r108243 which we plan to
> merge into HEAD. We would like that revision to be tested as much as possible
> and therefore we ask you to test ClangBSD to assure that the revision
> we are upda
On 15-07-2010 19:42, Roman Divacky wrote:
> I updated clang/LLVM in clangbsd to a newer version which I believe
> will fix thas. can you rene (and everyone else) please retest with
> updated ClangBSD and report back?
>
The updated version builds and installs fine, I'm now running the
clangbsd kern
I updated clang/LLVM in clangbsd to a newer version which I believe
will fix thas. can you rene (and everyone else) please retest with
updated ClangBSD and report back?
thank you!
On Thu, Jul 15, 2010 at 01:33:04PM +0200, Ren? Ladan wrote:
> 2010/7/14 Roman Divacky :
> > hi,
> >
> > ClangBSD was
2010/7/14 Roman Divacky :
> hi,
>
> ClangBSD was updated to LLVM/clang revision r108243 which we plan to
> merge into HEAD. We would like that revision to be tested as much as possible
> and therefore we ask you to test ClangBSD to assure that the revision
> we are updating to does not have some re
hi,
ClangBSD was updated to LLVM/clang revision r108243 which we plan to
merge into HEAD. We would like that revision to be tested as much as possible
and therefore we ask you to test ClangBSD to assure that the revision
we are updating to does not have some really embarassing bugs.
How to do it
