abhina.sreeskantharajan added a comment. In D95246#2568084 <https://reviews.llvm.org/D95246#2568084>, @ASDenysPetrov wrote:
> @jhenderson > >> @ASDenysPetrov, could you provide your link command-line for one of the >> tools that produces the failing message, please, e.g. llvm-ar? > > Here is output of running tests in llvm-ar folder: F15562458: > fail_output_llvm_ar.txt <https://reviews.llvm.org/F15562458> > >> Not that I'm saying we shouldn't try to fix your use-case, but if you aren't >> using Cygwin, it's worth noting that >> https://llvm.org/docs/GettingStarted.html#hardware states that only Visual >> Studio builds (whether via the IDE or some other tool like ninja) are known >> to work for Windows. > > I'm using MSYS2 instead of Cygwin. I found it as a better alternative. I'm > using GCC+MSYS2+Ninja. MSYS2 is based on a modified version of Cygwin according to its description, maybe if we can detect that in config.py this will solve your issue. Repository: rG LLVM Github Monorepo CHANGES SINCE LAST ACTION https://reviews.llvm.org/D95246/new/ https://reviews.llvm.org/D95246 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
