Unable to build CEF branch 3282

Having problems with building or using CEF's C/C++ APIs? This forum is here to help. Please do not post bug reports or feature requests here.

Unable to build CEF branch 3282

Postby ebahar » Mon Feb 05, 2018 1:22 am

Hi,
Im trying to build CEF on window 10 branch 3282.

the build command:
set CEF_USE_GN=1
set GN_DEFINES=is_win_fastlink=false is_official_build=true proprietary_codecs=true ffmpeg_branding=Chrome
set GYP_DEFINES=buildtype=Official
set GN_ARGUMENTS=--ide=vs2017 --sln=cef --filters=//cef/*
set GYP_MSVS_VERSION=2017
set CEF_ARCHIVE_FORMAT=tar.bz2
..\automate\automate-git.py --download-dir=f:\Src\cef\chromium_git\3282 --depot-tools-dir=f:\SRC\CEF\depot_tools\ --branch=3282 --no-debug --force-build --minimal-distrib


and i'm getting this error:
Applying issue #1999 fix to f:\Src\cef\chromium_git\3282\chromium\src\out\Debug_GN_x86_sandbox\obj\cef\libcef.ninja
--> f:\Src\cef\chromium_git\3282\chromium\src\out\Release_GN_x86\args.gn contents:
clang_use_chrome_plugins=false
enable_basic_printing=true
enable_nacl=false
enable_print_preview=false
enable_widevine=true
ffmpeg_branding="Chrome"
is_component_build=false
is_debug=false
is_official_build=true
is_win_fastlink=false
proprietary_codecs=true
target_cpu="x86"
-------- Running "ninja -C out\Release_GN_x86 cefclient" in "f:\Src\cef\chromium_git\3282\chromium\src"...
ninja: Entering directory `out\Release_GN_x86'
[1/122] ACTION //components/resources:about_credits(//build/toolchain/win:win_clang_x86)
--> f:\Src\cef\chromium_git\3282\chromium\src\out\Release_GN_x86_sandbox\args.gn contents:
clang_use_chrome_plugins=false
enable_basic_printing=true
enable_nacl=false
enable_print_preview=false
enable_widevine=true
ffmpeg_branding="Chrome"
is_component_build=false
is_debug=false
is_official_build=false
is_win_fastlink=false
proprietary_codecs=true
target_cpu="x86"
use_allocator_shim=false
-------- Running "ninja -C out\Release_GN_x86_sandbox cef_sandbox" in "f:\Src\cef\chromium_git\3282\chromium\src"...
ninja: Entering directory `out\Release_GN_x86_sandbox'
[1/373] CXX obj/base/base/precompile.cc.obj
FAILED: obj/base/base/precompile.cc.obj
../../third_party/llvm-build/Release+Asserts/bin/clang-cl.exe /nologo /showIncludes @obj/base/base/precompile.cc.obj.rsp /c ../../build/precompile.cc /Foobj/base/base/precompile.cc.obj /Fd"obj/base/base_cc.pdb"
Assertion failed: ID < FilenamesByID.size() && "Invalid FilenameID", file C:\b\rr\tmpcwzqyv\w\src\third_party\llvm\tools\clang\include\clang/Basic/SourceManagerInternals.h, line 105
Wrote crash dump file "C:\Users\ELAD~1.BAH\AppData\Local\Temp\clang-cl.exe-15de31.dmp"
LLVMSymbolizer: error reading file: PDB Error: Unable to load PDB. Make sure the file exists and is readable. Calling loadDataForExe

LLVMSymbolizer: error reading file: PDB Error: Unable to load PDB. Make sure the file exists and is readable. Calling loadDataForExe

LLVMSymbolizer: error reading file: PDB Error: Unable to load PDB. Make sure the file exists and is readable. Calling loadDataForExe

#0 0x00007ff763c6f276 (f:\Src\cef\chromium_git\3282\chromium\src\third_party\llvm-build\Release+Asserts\bin\clang-cl.exe+0x183f276)
#1 0x00007ff765a14179 (f:\Src\cef\chromium_git\3282\chromium\src\third_party\llvm-build\Release+Asserts\bin\clang-cl.exe+0x35e4179)
#2 0x00007ff765a105f8 (f:\Src\cef\chromium_git\3282\chromium\src\third_party\llvm-build\Release+Asserts\bin\clang-cl.exe+0x35e05f8)
#3 0x00007ff765a0432a (f:\Src\cef\chromium_git\3282\chromium\src\third_party\llvm-build\Release+Asserts\bin\clang-cl.exe+0x35d432a)
#4 0x00007ff765a043c6 (f:\Src\cef\chromium_git\3282\chromium\src\third_party\llvm-build\Release+Asserts\bin\clang-cl.exe+0x35d43c6)
#5 0x00007ff764b48f54 (f:\Src\cef\chromium_git\3282\chromium\src\third_party\llvm-build\Release+Asserts\bin\clang-cl.exe+0x2718f54)
#6 0x00007ff764b64df5 (f:\Src\cef\chromium_git\3282\chromium\src\third_party\llvm-build\Release+Asserts\bin\clang-cl.exe+0x2734df5)
#7 0x00007ff764b61a62 (f:\Src\cef\chromium_git\3282\chromium\src\third_party\llvm-build\Release+Asserts\bin\clang-cl.exe+0x2731a62)
#8 0x00007ff764b2ab29 (f:\Src\cef\chromium_git\3282\chromium\src\third_party\llvm-build\Release+Asserts\bin\clang-cl.exe+0x26fab29)
#9 0x00007ff7642ea77c (f:\Src\cef\chromium_git\3282\chromium\src\third_party\llvm-build\Release+Asserts\bin\clang-cl.exe+0x1eba77c)
#10 0x00007ff7642ea77c (f:\Src\cef\chromium_git\3282\chromium\src\third_party\llvm-build\Release+Asserts\bin\clang-cl.exe+0x1eba77c)
#11 0x00007ff764a0b152 (f:\Src\cef\chromium_git\3282\chromium\src\third_party\llvm-build\Release+Asserts\bin\clang-cl.exe+0x25db152)
#12 0x00007ff7642a6860 (f:\Src\cef\chromium_git\3282\chromium\src\third_party\llvm-build\Release+Asserts\bin\clang-cl.exe+0x1e76860)
#13 0x00007ff764291071 (f:\Src\cef\chromium_git\3282\chromium\src\third_party\llvm-build\Release+Asserts\bin\clang-cl.exe+0x1e61071)
#14 0x00007ff76431d133 (f:\Src\cef\chromium_git\3282\chromium\src\third_party\llvm-build\Release+Asserts\bin\clang-cl.exe+0x1eed133)
#15 0x00007ff762436d2e (f:\Src\cef\chromium_git\3282\chromium\src\third_party\llvm-build\Release+Asserts\bin\clang-cl.exe+0x6d2e)
#16 0x00007ff7624347cf (f:\Src\cef\chromium_git\3282\chromium\src\third_party\llvm-build\Release+Asserts\bin\clang-cl.exe+0x47cf)
#17 0x00007ff7659fb4c5 (f:\Src\cef\chromium_git\3282\chromium\src\third_party\llvm-build\Release+Asserts\bin\clang-cl.exe+0x35cb4c5)
#18 0x00007ffc94ee1fe4 (C:\WINDOWS\System32\KERNEL32.DLL+0x11fe4)
#19 0x00007ffc9577efb1 (C:\WINDOWS\SYSTEM32\ntdll.dll+0x6efb1)
clang-cl.exe: error: clang frontend command failed due to signal (use -v to see invocation)
clang version 6.0.0 (trunk 318667)
Target: i386-pc-windows-msvc
Thread model: posix
InstalledDir: f:\src\cef\chromium_git\3282\chromium\src\third_party\llvm-build\Release+Asserts\bin
clang-cl.exe: note: diagnostic msg: PLEASE submit a bug report to http://llvm.org/bugs/ and include the crash backtrace, preprocessed source, and associated run script.
clang-cl.exe: note: diagnostic msg:
********************

PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT:
Preprocessed source(s) and associated run script(s) are located at:
clang-cl.exe: note: diagnostic msg: C:\Users\ELAD~1.BAH\AppData\Local\Temp\precompile-b5c81f.sh
clang-cl.exe: note: diagnostic msg:

********************
[2/373] CXX obj/sandbox/win/sandbox/precompile.cc.obj
FAILED: obj/sandbox/win/sandbox/precompile.cc.obj
../../third_party/llvm-build/Release+Asserts/bin/clang-cl.exe /nologo /showIncludes @obj/sandbox/win/sandbox/precompile.cc.obj.rsp /c ../../build/precompile.cc /Foobj/sandbox/win/sandbox/precompile.cc.obj /Fd"obj/sandbox/win/sandbox_cc.pdb"
Assertion failed: ID < FilenamesByID.size() && "Invalid FilenameID", file C:\b\rr\tmpcwzqyv\w\src\third_party\llvm\tools\clang\include\clang/Basic/SourceManagerInternals.h, line 105
Wrote crash dump file "C:\Users\ELAD~1.BAH\AppData\Local\Temp\clang-cl.exe-2ca767.dmp"
LLVMSymbolizer: error reading file: PDB Error: Unable to load PDB. Make sure the file exists and is readable. Calling loadDataForExe

LLVMSymbolizer: error reading file: PDB Error: Unable to load PDB. Make sure the file exists and is readable. Calling loadDataForExe

LLVMSymbolizer: error reading file: PDB Error: Unable to load PDB. Make sure the file exists and is readable. Calling loadDataForExe

#0 0x00007ff763c6f276 (f:\Src\cef\chromium_git\3282\chromium\src\third_party\llvm-build\Release+Asserts\bin\clang-cl.exe+0x183f276)
#1 0x00007ff765a14179 (f:\Src\cef\chromium_git\3282\chromium\src\third_party\llvm-build\Release+Asserts\bin\clang-cl.exe+0x35e4179)
#2 0x00007ff765a105f8 (f:\Src\cef\chromium_git\3282\chromium\src\third_party\llvm-build\Release+Asserts\bin\clang-cl.exe+0x35e05f8)
#3 0x00007ff765a0432a (f:\Src\cef\chromium_git\3282\chromium\src\third_party\llvm-build\Release+Asserts\bin\clang-cl.exe+0x35d432a)
#4 0x00007ff765a043c6 (f:\Src\cef\chromium_git\3282\chromium\src\third_party\llvm-build\Release+Asserts\bin\clang-cl.exe+0x35d43c6)
#5 0x00007ff764b48f54 (f:\Src\cef\chromium_git\3282\chromium\src\third_party\llvm-build\Release+Asserts\bin\clang-cl.exe+0x2718f54)
#6 0x00007ff764b64df5 (f:\Src\cef\chromium_git\3282\chromium\src\third_party\llvm-build\Release+Asserts\bin\clang-cl.exe+0x2734df5)
#7 0x00007ff764b61a62 (f:\Src\cef\chromium_git\3282\chromium\src\third_party\llvm-build\Release+Asserts\bin\clang-cl.exe+0x2731a62)
#8 0x00007ff764b2ab29 (f:\Src\cef\chromium_git\3282\chromium\src\third_party\llvm-build\Release+Asserts\bin\clang-cl.exe+0x26fab29)
#9 0x00007ff7642ea77c (f:\Src\cef\chromium_git\3282\chromium\src\third_party\llvm-build\Release+Asserts\bin\clang-cl.exe+0x1eba77c)
#10 0x00007ff7642ea77c (f:\Src\cef\chromium_git\3282\chromium\src\third_party\llvm-build\Release+Asserts\bin\clang-cl.exe+0x1eba77c)
#11 0x00007ff764a0b152 (f:\Src\cef\chromium_git\3282\chromium\src\third_party\llvm-build\Release+Asserts\bin\clang-cl.exe+0x25db152)
#12 0x00007ff7642a6860 (f:\Src\cef\chromium_git\3282\chromium\src\third_party\llvm-build\Release+Asserts\bin\clang-cl.exe+0x1e76860)
#13 0x00007ff764291071 (f:\Src\cef\chromium_git\3282\chromium\src\third_party\llvm-build\Release+Asserts\bin\clang-cl.exe+0x1e61071)
#14 0x00007ff76431d133 (f:\Src\cef\chromium_git\3282\chromium\src\third_party\llvm-build\Release+Asserts\bin\clang-cl.exe+0x1eed133)
#15 0x00007ff762436d2e (f:\Src\cef\chromium_git\3282\chromium\src\third_party\llvm-build\Release+Asserts\bin\clang-cl.exe+0x6d2e)
#16 0x00007ff7624347cf (f:\Src\cef\chromium_git\3282\chromium\src\third_party\llvm-build\Release+Asserts\bin\clang-cl.exe+0x47cf)
#17 0x00007ff7659fb4c5 (f:\Src\cef\chromium_git\3282\chromium\src\third_party\llvm-build\Release+Asserts\bin\clang-cl.exe+0x35cb4c5)
#18 0x00007ffc94ee1fe4 (C:\WINDOWS\System32\KERNEL32.DLL+0x11fe4)
#19 0x00007ffc9577efb1 (C:\WINDOWS\SYSTEM32\ntdll.dll+0x6efb1)
clang-cl.exe: error: clang frontend command failed due to signal (use -v to see invocation)
clang version 6.0.0 (trunk 318667)
Target: i386-pc-windows-msvc
Thread model: posix
InstalledDir: f:\src\cef\chromium_git\3282\chromium\src\third_party\llvm-build\Release+Asserts\bin
clang-cl.exe: note: diagnostic msg: PLEASE submit a bug report to http://llvm.org/bugs/ and include the crash backtrace, preprocessed source, and associated run script.
clang-cl.exe: note: diagnostic msg:
********************

PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT:
Preprocessed source(s) and associated run script(s) are located at:
clang-cl.exe: note: diagnostic msg: C:\Users\ELAD~1.BAH\AppData\Local\Temp\precompile-b48cce.sh
clang-cl.exe: note: diagnostic msg:

********************
ninja: build stopped: subcommand failed.
Traceback (most recent call last):
File "F:\src\cef\automate_63\automate-git.py", line 1119, in <module>
if options.buildlogfile else None)
File "F:\src\cef\automate_63\automate-git.py", line 55, in run
args, cwd=working_dir, env=env, shell=(sys.platform == 'win32'))
File "C:\Python27\lib\subprocess.py", line 540, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['ninja', '-C', 'out\\Release_GN_x86_sandbox', 'cef_sandbox']' returned non-zero exit status 1



thanks for help..
ebahar
Techie
 
Posts: 46
Joined: Tue Nov 22, 2016 3:52 am

Re: Unable to build CEF branch 3282

Postby ndesktop » Mon Feb 05, 2018 3:26 am

Looks like a pch-related llvm crash.
I'd try to ninja -t clean, or manually delete .pch files from the out build directory and retry. Not sure if this will do it, sure, but this is what I'd do.

Edit: looks like 780124 Chromium issue. It seems related to VS 2015.5 but not 2017.
ndesktop
Master
 
Posts: 750
Joined: Thu Dec 03, 2015 10:10 am

Re: Unable to build CEF branch 3282

Postby magreenblatt » Mon Feb 05, 2018 12:02 pm

Correct, add enable_precompiled_headers=false to GN_DEFINES.
magreenblatt
Site Admin
 
Posts: 12382
Joined: Fri May 29, 2009 6:57 pm

Re: Unable to build CEF branch 3282

Postby ebahar » Tue Feb 06, 2018 6:35 am

worked,

thanks!
ebahar
Techie
 
Posts: 46
Joined: Tue Nov 22, 2016 3:52 am


Return to Support Forum

Who is online

Users browsing this forum: No registered users and 37 guests

cron