Windows build fails on VS community 2017 15.5.2
Reported by
halton....@gmail.com,
Dec 26 2017
|
|||||
Issue description
UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3253.3 Safari/537.36
Steps to reproduce the problem:
* OS: Windows 10 Enterprise 64bit 1607
* Visual Studio: Community 2017 15.5.2
* Windows SDK: 10.0.15063.468
What is the expected behavior?
Able to build chromium on windows
What went wrong?
ninja: Entering directory `out\Release_x64_shared\'
[4/58034] CXX obj/base/check_example/check_example.obj
FAILED: obj/base/check_example/check_example.obj
../../third_party/llvm-build/Release+Asserts/bin/clang-cl.exe /nologo /showIncludes @obj/base/check_example/check_example.obj.rsp /c ../../base/check_example.cc /Foobj/base/check_example/check_example.obj /Fd"obj/base/check_example_cc.pdb"
In file included from ../..\build/build_config.h:8:
In file included from ../..\base/compiler_specific.h:8:
In file included from ../..\build/build_config.h:9:
In file included from ../..\base/logging.h:12:
In file included from c:\program files (x86)\microsoft visual studio\2017\community\vc\tools\msvc\14.12.25827\include\sstream:6:
In file included from c:\program files (x86)\microsoft visual studio\2017\community\vc\tools\msvc\14.12.25827\include\string:6:
In file included from c:\program files (x86)\microsoft visual studio\2017\community\vc\tools\msvc\14.12.25827\include\istream:6:
In file included from c:\program files (x86)\microsoft visual studio\2017\community\vc\tools\msvc\14.12.25827\include\ostream:6:
In file included from c:\program files (x86)\microsoft visual studio\2017\community\vc\tools\msvc\14.12.25827\include\ios:6:
In file included from c:\program files (x86)\microsoft visual studio\2017\community\vc\tools\msvc\14.12.25827\include\xlocnum:10:
In file included from c:\program files (x86)\microsoft visual studio\2017\community\vc\tools\msvc\14.12.25827\include\streambuf:6:
In file included from c:\program files (x86)\microsoft visual studio\2017\community\vc\tools\msvc\14.12.25827\include\xiosbase:6:
In file included from c:\program files (x86)\microsoft visual studio\2017\community\vc\tools\msvc\14.12.25827\include\xlocale:8:
In file included from c:\program files (x86)\microsoft visual studio\2017\community\vc\tools\msvc\14.12.25827\include\stdexcept:7:
In file included from c:\program files (x86)\microsoft visual studio\2017\community\vc\tools\msvc\14.12.25827\include\xstring:6:
In file included from c:\program files (x86)\microsoft visual studio\2017\community\vc\tools\msvc\14.12.25827\include\xmemory0:6:
c:\program files (x86)\microsoft visual studio\2017\community\vc\tools\msvc\14.12.25827\include\cstdint(10,13): error: no member named 'int8_t' in the global namespace; did you mean 'wint_t'?
using _CSTD int8_t; using _CSTD int16_t;
~~~~~ ^
c:\program files (x86)\windows kits\10\include\10.0.15063.0\ucrt\corecrt.h(477,39): note: 'wint_t' declared here
typedef unsigned short wint_t;
^
Did this work before? N/A
Chrome version: 64.0.3253.3 Channel: canary
OS Version: 10
Flash Version:
,
Dec 29 2017
As this issue is related to Build, hence adding the label as TE-NeedsTriageHelp, can anyone from the Dev team please have a look at this issue Thanks!
,
Jan 19 2018
Checked again ddccd3f6 at Jan 17, this issue still exists. Notice https://groups.google.com/a/chromium.org/forum/#!msg/chromium-dev/Y3OEIKkdlu0/TCcT1SvwAwAJ is use clang by default, after I use "is_clang=false", the issue disappears. Isn't clang unable to build windows build?
,
Jan 24 2018
,
Jan 29 2018
I'll take a look. Chrome currently builds with VC++ 15.3. 15.5 has had various problems, although last time I tested it worked. It's not immediately clear whether this is a clang bug or a VC++ header-file bug that VC++ happens to handle.
,
Jan 29 2018
I just did a test build of obj/base/check_example/check_example.obj with VS 15.5.2 and had no problems. As mentioned in the previous comment the bug looks like a problem with the VC++ header files. I suspect you have a corrupt install, or else there is a bug in the community version. I tested with VS 15.5.2 professional, although I would expect the header files to be identical.
In my version of cstdint (found at C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\VC\Tools\MSVC\14.12.25827\include\cstdint) the file starts off like this:
// cstdint standard header
#pragma once
#ifndef _CSTDINT_
#define _CSTDINT_
#include <yvals.h>
#include <stdint.h>
#ifndef RC_INVOKED
_STD_BEGIN
using _CSTD int8_t; using _CSTD int16_t;
Note that it includes stdint.h and then references int8_t. Maybe try preprocessing the file. To do this run ninja with the -v option:
ninja -v -C out\default obj/base/check_example/check_example.obj
You can then CD to out\default, take the build command that was printed, change the slashes to back slashes in the path to clang-cl.exe, and check the list of header files being compiled to see if stdint.h is coming from somewhere unexpected. If that doesn't help then try again with /showIncludes replaced with /P. Redirect it to a file and inspect it to figure out what is going on.
For now I'm closing this as WontFix, no-repro.
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by krajshree@chromium.org
, Dec 26 2017