New issue
Advanced search Search tips

Issue 759266 link

Starred by 2 users
Status: Duplicate
Merged: issue 760385
Owner: ----
Closed: Aug 2017
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 3
Type: Bug



Sign in to add a comment

CrWinClangLLD failing compile with undefined symbol: _RequestSingleCrashUploadImpl

Project Member Reported by inglorion@chromium.org, Aug 26 2017 
Example: https://build.chromium.org/p/chromium.fyi/builders/CrWinClangLLD/builds/5916

Logs: https://luci-logdog.appspot.com/v/?s=chromium%2Fbb%2Fchromium.fyi%2FCrWinClangLLD%2F5916%2F%2B%2Frecipes%2Fsteps%2Fcompile%2F0%2Fstdout

Excerpt:
[10195/51201] LINK(DLL) chrome_elf.dll chrome_elf.dll.lib
FAILED: chrome_elf.dll chrome_elf.dll.lib 
C:/b/depot_tools/win_tools-2_7_6_bin/python/bin/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_elf.dll.lib /DLL /OUT:./chrome_elf.dll /PDB:./chrome_elf.dll.pdb @./chrome_elf.dll.rsp
..\..\third_party\llvm-build\Release+Asserts\bin\lld-link.exe: warning: error with internal manifest tool: no libxml2
..\..\third_party\llvm-build\Release+Asserts\bin\lld-link.exe: warning: <root>: undefined symbol: _RequestSingleCrashUploadImpl
error: link failed

First failing build: https://build.chromium.org/p/chromium.fyi/builders/CrWinClangLLD/builds/5909

Last successful build: https://build.chromium.org/p/chromium.fyi/builders/CrWinClangLLD/builds/5908

Comment 1 by robrich...@gmail.com, Aug 28 2017 

Happening with my local WinClangLLD(64) builds as well.

Appears potentially to be the result of the following commit considering the RequestSingleCrashUploadImpl error and time frame involved:

https://chromium.googlesource.com/chromium/src/+/86ac09aa98e574ca69c9cd090f105683294a64b0

Comment 2 by robrich...@gmail.com, Aug 28 2017 

Suspect commit 86ac09aa98e574ca69c9cd090f105683294a64b0 confirmed here.

Pulled a LKCR from today, reverted the above commit locally, and got a working CrWinClangLLD64 build without the missing symbol link error.

Comment 3 by robrich...@gmail.com, Aug 29 2017 

Quick FYI. Today's e8cffa346e84dfa2a14653194a685301c88b3ecf touches many of the same files as 86ac09aa98e574ca69c9cd090f105683294a64b0 , so I had to revert both of them to get around the missing symbol error link error my latest CrWinClangLLD64 local build.

Comment 4 by h...@chromium.org, Aug 31 2017

Mergedinto: 760385
Status: Duplicate (was: Unconfirmed)
►

Sign in to add a comment