[llvm-bugs] [Bug 27234] New: clang-cl incorrectly complains about missing lib file if it's in a subdir and "/link /libpath:sub" is passed

[via llvm-bugs]

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

            Bug ID: 27234
           Summary: clang-cl incorrectly complains about missing lib file
                    if it's in a subdir and "/link /libpath:sub" is passed
           Product: clang
           Version: unspecified
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: normal
          Priority: P
         Component: Driver
          Assignee: unassignedclangbugs at nondot.org
          Reporter: nicolasweber at gmx.de
                CC: llvm-bugs at lists.llvm.org
    Classification: Unclassified

The following works with cl:

C:\src\tmp>type sub\f.cc
int f() { return 42; }

C:\src\tmp>type main.cc
int f();
int main() { return f(); }

C:\src\tmp>cl /nologo /c sub\f.cc /Fosub\f.obj
f.cc

C:\src\tmp>lib /nologo /out:sub\f.lib sub\f.obj

C:\src\tmp>cl /nologo /c main.cc
main.cc

C:\src\tmp>cl /nologo main.obj f.lib /link /libpath:sub



If I do the same with clang-cl, the last step fails like so:

C:\src\tmp>c:\src\llvm-build\bin\clang-cl main.obj f.lib /link /libpath:sub
clang-cl.exe: error: no such file or directory: 'f.lib'


I found this while trying to build ninja with clang-cl, which happens to use
this setup.


(Also, cl also accepts "/link/libpath:sub" without a space and clang-cl
doesn't. I found this while fatfingering the repro above.)

-- 
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/20160406/72d84ce5/attachment.html>