Hello NightStrike -
On Sat, Oct 16, 2010 at 1:06 PM, NightStrike wrote:
> On Fri, Oct 15, 2010 at 3:43 PM, K. Frank wrote:
>> Is there a practical way to get the experimental code into the hands of
>> people who run the test suite or do other kinds of testing, especially on
>> platforms other th
On Fri, Oct 15, 2010 at 3:43 PM, K. Frank wrote:
> Is there a practical way to get the experimental code into the hands of
> people who run the test suite or do other kinds of testing, especially on
> platforms other than 64-bit windows 7 (and the particular builds of mingw32
> and mingw-w64 that
Hi Kai -
A minor question about error numbers...
On Sat, Oct 16, 2010 at 4:11 AM, Kai Tietz wrote:
> 2010/10/16 Ruben Van Boxem :
>> Hi,
>> I have started trying to build Clang with mingw-w64 tools. The x64 build
>> fails because an LLVM tool called tblgen is miscompiled, so I tried a x86
>> bui
2010/10/16 Ruben Van Boxem :
> Hi,
> I have started trying to build Clang with mingw-w64 tools. The x64 build
> fails because an LLVM tool called tblgen is miscompiled, so I tried a x86
> build instead for now. This works until the utterly final step, and some
> error types are undeclared:
>>
>> M:
On Sat, Oct 16, 2010 at 11:00 AM, Ruben Van Boxem
wrote:
> Hi,
> I have started trying to build Clang with mingw-w64 tools. The x64 build
> fails because an LLVM tool called tblgen is miscompiled, so I tried a x86
> build instead for now. This works until the utterly final step, and some
> error t
Hi,
I have started trying to build Clang with mingw-w64 tools. The x64 build
fails because an LLVM tool called tblgen is miscompiled, so I tried a x86
build instead for now. This works until the utterly final step, and some
error types are undeclared:
M:\Development\Source\LLVM\utils\KillTheDocto
