New issue
Advanced search Search tips

Issue 759265 link

Starred by 2 users
Status: Verified
Owner: ----
Closed: Sep 2017
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 3
Type: Bug



Sign in to add a comment

CrWinClangLLD complains: error with internal manifest tool: no libxml2

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:
[10207/51201] LINK alternate_version_generator.exe
..\..\third_party\llvm-build\Release+Asserts\bin\lld-link.exe: warning: error with internal manifest tool: no libxml2
[10208/51201] LINK gcapi_test.exe
..\..\third_party\llvm-build\Release+Asserts\bin\lld-link.exe: warning: error with internal manifest tool: no libxml2

Comment 1 by inglorion@chromium.org, Aug 26 2017 

This message is present even in succeeding builds, so it's not causing builds to fail, just making noise.

Comment 2 by ecbeckmann@google.com, Aug 28 2017 

Sorry this is due to a warning I added.  This message should only be given if BOTH internal manifest tool and external mt.exe fail.  Will fix this shortly.

Comment 4 by ecbeckmann@google.com, Sep 6 2017 

fixed in r312604

Comment 5 by ecbeckmann@google.com, Sep 6 2017 

@inglorion could you close this?  I can't seem to take ownership of this.

Comment 6 by inglorion@chromium.org, Sep 7 2017

Status: Verified (was: Unconfirmed)
Verified that the message is not appearing in the build logs anymore. Thanks, Eric!
►

Sign in to add a comment