[llvm-bugs] [Bug 34291] New: When attempting to compile/link Windows target from a WSL bash instance the driver attempts to load windows linker

[via llvm-bugs]

https://bugs.llvm.org/show_bug.cgi?id=34291

            Bug ID: 34291
           Summary: When attempting to compile/link Windows target from a
                    WSL bash instance the driver attempts to load windows
                    linker
           Product: clang
           Version: 5.0
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P
         Component: Driver
          Assignee: unassignedclangbugs at nondot.org
          Reporter: rennieallen at gmail.com
                CC: llvm-bugs at lists.llvm.org

Invocation (simple single function c source file):

$ clang -target x86_64-pc-windows-msvc18.0.0 -fuse-ld=lld -o foo.exe foo.c
clang: warning: unable to find a Visual Studio installation; try running Clang
from a developer command prompt [-Wmsvc-not-found]
clang: error: unable to execute command: Executable "lld-link.exe" doesn't
exist!
clang: error: linker command failed with exit code 1 (use -v to see invocation)

The missing Visual Studio installation can presumably be easily rectified, but
the concern is the "lld-link.exe doesn't exist" error. 

My understanding (perhaps I am wrong) is that lld on Linux should be able to
link a Windows executable as of 5.0, and that if the driver is Linux hosted it
should invoke the Linux hosted lld even when a windows target is selected.

Version confirmation:
$ which clang
/usr/local/bin/clang
$ clang --version
clang version 5.0.0 (http://root.cern.ch/git/clang.git
1f8b137c7eb06ed8e321649ef7e3f3e7a96f361c) (http://root.cern.ch/git/llvm.git
2a34248cb945d63ded5ee55128e68efd7e5b87c8)
Target: x86_64-unknown-linux-gnu
Thread model: posix
InstalledDir: /usr/local/bin

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20170823/f2c3f240/attachment.html>