search for: stl_uninitialized

....) at /usr/include/c++/4.5/bits/stl_algobase.h:442 #4 copy<char const*, char*> (this=0x806fae8, Asm=..., Layout=...) at /usr/include/c++/4.5/bits/stl_algobase.h:474 #5 uninitialized_copy<char const*, char*> (this=0x806fae8, Asm=..., Layout=...) at /usr/include/c++/4.5/bits/stl_uninitialized.h:92 #6 uninitialized_copy<char const*, char*> (this=0x806fae8, Asm=..., Layout=...) at /usr/include/c++/4.5/bits/stl_uninitialized.h:116 #7 append<char const*> (this=0x806fae8, Asm=..., Layout=...) at /home/matt/src/llvm-2.8/include/llvm/ADT/SmallVector.h:364 #8 operator+= (...

...well-known problem. Another source of such problems is 'sort' util. > Probably not an issue, but I see in the coding standards chris likes > warnings to be treated like errors. Is there something else I am missing? > Perhaps an env setting to disable those warnings? The mentioned stl_uninitialized warnings are harmless and comes from compiler bug. Unfortunately, there is no way to "turn them off". -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University

Hi Anton, The problem is in getting the system configured. Below is the crash I get in configure. Your comment regarding gnuwin32 not being needed is interesting - I actually installed gnu bison/flex to get past an earlier crash in configure. Thats why I was suggesting that a precompiled OBJ_ROOT for MingW32 would be a good idea - configure appears to be inherently fragile, and requires more