Anton Korobeynikov wrote: >> it has been fixed in clang but not in llvm-gcc. > I believe I fixed it in llvm-gcc via fixincludes :) Not the best way, but... For example, it doesn't help dragonegg unless the fixincludes patch goes upstream. Ciao, Duncan.