Martin Storsjö

> Well, after reading what @alvinhochun wrote, I am convinced that toolchains should not include third party libraries. If you do want to include zlib, then just a static lib...

I can reproduce this. (Note to other readers and future self: the source files are saved as utf8, and cl.exe is called with the `/utf-8` flag.) I'll see if I...

FWIW, I did dig deeper into this, but it looks like this is fairly nontrivial to fix. The streams `std::cout` and `std::wcout` in libc++ don't seem to react to and...

I've posted an initial patch that tries to fix this issue at https://reviews.llvm.org/D146398.

The fix for this landed in https://github.com/llvm/llvm-project/commit/fcbbd9649ac165aaf7fc7d60b8fef3b23755179a, and the latest nightly build at https://github.com/mstorsjo/llvm-mingw/releases/tag/nightly contains a version with this fix.

There's now a prerelease with LLVM 17.0.0 RC1, at https://github.com/mstorsjo/llvm-mingw/releases/tag/20230730, with this fix too.

Indeed, polly isn't enabled in the builds here. Overall, the philosophy of llvm-mingw isn't to enable everything that possibly could be useful, but a pragmatic tradeoff between effort/overhead and actual...

I cannot reproduce any such build problem with the repo you provided. To get a third party reproducible setup, I would recommend trying to reproduce the issue in e.g. GitHub...

With the tools placed in a path with spaces, I can indeed reproduce issues. And the issues are most probably caused by the wrapper executables indeed. > If I am...

(Or as a separate sidetrack - is there any way to ask the CMake generator to not flatten paths to 8.3 paths, trusting that the tools themselves can handle arguments/paths...