[llvm-bugs] [Bug 36478] New: Make lld-link.exe detect that the result file is in use and that linking will fail.

[via llvm-bugs]

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

            Bug ID: 36478
           Summary: Make lld-link.exe detect that the result file is in
                    use and that linking will fail.
           Product: lld
           Version: unspecified
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: enhancement
          Priority: P
         Component: All Bugs
          Assignee: unassignedbugs at nondot.org
          Reporter: pbos at google.com
                CC: llvm-bugs at lists.llvm.org

When building chrome (and I have chrome.exe running), linking completes and
fails when the result is about to be written to disk:

[519/542] LINK(DLL) chrome.dll chrome.dll.lib chrome.dll.pdb
FAILED: chrome.dll chrome.dll.lib chrome.dll.pdb
C:/python_27_amd64/files/python.exe ../../build/toolchain/win/tool_wrapper.py
link-wrapper environment.x86 False
../../third_party/llvm-build/Release+Asserts/bin/lld-link.exe /nologo
/IMPLIB:./chrome.dll.lib /DLL /OUT:./chrome.dll /PDB:./chrome.dll.pdb
@./chrome.dll.rsp
..\..\third_party\llvm-build\Release+Asserts\bin\lld-link.exe: error: failed to
write the output file: permission denied
[538/542] CXX
obj/chrome/test/browser_tests/better_session_restore_browsertest.obj

Since linking can take minutes it'd be nice if this case could (best-effort) be
caught on startup rather than when all work is done.

-- 
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/20180222/6a261613/attachment.html>