mstorsjo added a comment. In D68980#1709314 <https://reviews.llvm.org/D68980#1709314>, @labath wrote:
> Yeah, I raised this issue back when build.py was first introduced, but it did > not really get resolved properly. (Back then, windows arm wasn't considered, > so I guess the issue wasn't seen as pressing.) Well, windows arm doesn't really affect this aspect at all. But if windows arm didn't exist, then clang-cl would probably error out more directly when run on arm linux, unless given an explicit architecture option. > Right now, build.py has a sort of a split personality, where it generally > builds stuff for the host, *except* if it uses the clang-cl driver, where it > builds stuff for x86 windows, regardless of what happens to be the host > platform. Yes, that does seem like the root of the problem. Repository: rLLDB LLDB CHANGES SINCE LAST ACTION https://reviews.llvm.org/D68980/new/ https://reviews.llvm.org/D68980 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
