<div dir="ltr"><div>It seems the change of the commit was disabled by default at r325296.</div><div><br></div><div>Regards.</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">2018-02-19 19:55 GMT+09:00 Hans Wennborg <span dir="ltr"><<a href="mailto:hans@chromium.org" target="_blank">hans@chromium.org</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">No, I didn't change anything here and I don't think Zach did either.<br>
<div class="HOEnZb"><div class="h5"><br>
On Sun, Feb 18, 2018 at 9:39 AM, masaru tsuchiyama <<a href="mailto:m.tmatma@gmail.com">m.tmatma@gmail.com</a>> wrote:<br>
> It didn't happen at r325456.<br>
> Did you fix it?<br>
><br>
> Regards.<br>
><br>
> 2018-02-17 5:57 GMT+09:00 masaru tsuchiyama <<a href="mailto:m.tmatma@gmail.com">m.tmatma@gmail.com</a>>:<br>
>><br>
>> > Is that a solution to your problem?<br>
>><br>
>> No.<br>
>> It could be a workaround, but not a solution.<br>
>> I think we need to know the reason why the commit and the option affect<br>
>> the result at least.<br>
>><br>
>><br>
>> 2018-02-16 19:05 GMT+09:00 Hans Wennborg <<a href="mailto:hans@chromium.org">hans@chromium.org</a>>:<br>
>>><br>
>>> On Thu, Feb 15, 2018 at 11:43 PM, masaru tsuchiyama <<a href="mailto:m.tmatma@gmail.com">m.tmatma@gmail.com</a>><br>
>>> wrote:<br>
>>> > Hi,<br>
>>> ><br>
>>> >> Is there any info about what went wrong in NSISOutput.log?<br>
>>> ><br>
>>> > I attach the log.<br>
>>> ><br>
>>> > This is the last part of the log.<br>
>>> ><br>
>>> > File: "clangStaticAnalyzerCheckers.<wbr>lib"<br>
>>> ><br>
>>> > Internal compiler error #12345: error mmapping file <a href="tel:%282106828838" value="+12106828838">(2106828838</a>,<br>
>>> > 33554432)<br>
>>> > is out of range.<br>
>>> > Note: you may have one or two (large) stale temporary file(s) left in<br>
>>> > your<br>
>>> > temporary directory (Generally this only happens on Windows 9x).<br>
>>> ><br>
>>> > I'm using Win10 Pro Japanese and VS2017 Community Japanese.<br>
>>> > The version of NSIS is 3.02.1.<br>
>>> ><br>
>>> >> Maybe you want to add -DLLVM_INSTALL_TOOLCHAIN_ONLY=<wbr>ON to your build,<br>
>>> >> though I'm not sure that should make any difference to the pdb files.<br>
>>> ><br>
>>> > If I added the option, the build succeeded.<br>
>>><br>
>>> Is that a solution to your problem?<br>
>>><br>
>>> > 2018-02-14 23:06 GMT+09:00 Hans Wennborg <<a href="mailto:hans@chromium.org">hans@chromium.org</a>>:<br>
>>> >><br>
>>> >> +Zach for r324504<br>
>>> >><br>
>>> >> On Tue, Feb 13, 2018 at 1:45 PM, masaru tsuchiyama via cfe-users<br>
>>> >> <<a href="mailto:cfe-users@lists.llvm.org">cfe-users@lists.llvm.org</a>> wrote:<br>
>>> >> > Hello<br>
>>> >> ><br>
>>> >> > llvm build fails at r324504 or later.<br>
>>> >> > I used the attached file to build. (renamed to .txt)<br>
>>> >> ><br>
>>> >> > example:<br>
>>> >> > clang-build.bat ninja x86 update 324806<br>
>>> >> ><br>
>>> >> > This is the tail of the failure log.<br>
>>> >> ><br>
>>> >> > CPack: Create package using NSIS<br>
>>> >> > CPack: Install projects<br>
>>> >> > CPack: - Install project: LLVM<br>
>>> >> > Creating llvm-ranlib.exe<br>
>>> >> > Creating llvm-lib.exe<br>
>>> >> > Creating llvm-dlltool.exe<br>
>>> >> > Creating clang++.exe<br>
>>> >> > Creating clang-cl.exe<br>
>>> >> > Creating clang-cpp.exe<br>
>>> >> > Creating ../msbuild-bin/cl.exe<br>
>>> >> > Creating lld-link.exe<br>
>>> >> > Creating ld.lld.exe<br>
>>> >> > Creating ld64.lld.exe<br>
>>> >> > Creating wasm-ld.exe<br>
>>> >> > Creating llvm-readelf.exe<br>
>>> >> > CPack: Create package<br>
>>> >> > CPack Error: Problem running NSIS command: "C:/Program Files<br>
>>> >> > (x86)/NSIS/makensis.exe"<br>
>>> >> ><br>
>>> >> > "C:/Jenkins/workspace/llvm/<wbr>build/_CPack_Packages/win32/<wbr>NSIS/project.nsi"<br>
>>> >> > Please check<br>
>>> >> ><br>
>>> >> ><br>
>>> >> > C:/Jenkins/workspace/llvm/<wbr>build/_CPack_Packages/win32/<wbr>NSIS/NSISOutput.log<br>
>>> >> > for errors<br>
>>> >><br>
>>> >> Is there any info about what went wrong in NSISOutput.log?<br>
>>> >><br>
>>> >> > CPack Error: Problem compressing the directory<br>
>>> >> > CPack Error: Error when generating package: LLVM<br>
>>> >> > FAILED: CMakeFiles/package.util<br>
>>> >> > cmd.exe /C "cd /D C:\Jenkins\workspace\llvm\<wbr>build && "C:\Program<br>
>>> >> > Files\CMake\bin\cpack.exe" --config ./CPackConfig.cmake"<br>
>>> >> > ninja: build stopped: subcommand failed.<br>
>>> >> ><br>
>>> >> > I confirmed that the build succeeded by reverting r324504 at<br>
>>> >> > r324806.<br>
>>> >> ><br>
>>> >> > Index: cmake/modules/<wbr>HandleLLVMOptions.cmake<br>
>>> >> > ==============================<wbr>==============================<wbr>=======<br>
>>> >> > --- cmake/modules/<wbr>HandleLLVMOptions.cmake (revision 324806)<br>
>>> >> > +++ cmake/modules/<wbr>HandleLLVMOptions.cmake (working copy)<br>
>>> >> > @@ -353,12 +353,6 @@<br>
>>> >> ><br>
>>> >> > append("/Zc:inline" CMAKE_C_FLAGS CMAKE_CXX_FLAGS)<br>
>>> >> ><br>
>>> >> > - # Generate PDB even in release for profiling.<br>
>>> >> > - if (uppercase_CMAKE_BUILD_TYPE STREQUAL "RELEASE")<br>
>>> >> > - append("/Zi" CMAKE_C_FLAGS CMAKE_CXX_FLAGS)<br>
>>> >> > - append("/DEBUG" CMAKE_EXE_LINKER_FLAGS<br>
>>> >> > CMAKE_MODULE_LINKER_FLAGS<br>
>>> >> > CMAKE_SHARED_LINKER_FLAGS)<br>
>>> >> > - endif (uppercase_CMAKE_BUILD_TYPE STREQUAL "RELEASE")<br>
>>> >> > -<br>
>>> >><br>
>>> >> This is surprising. I wouldn't expect the PDB files to end up in the<br>
>>> >> package or otherwise affect it. In fact, I tried building a package<br>
>>> >> with the script in utils/release/build_llvm_<wbr>package.bat at r324504 and<br>
>>> >> it worked fine for me. And I verified there were no pdbs in the<br>
>>> >> package.<br>
>>> >><br>
>>> >> Maybe you want to add -DLLVM_INSTALL_TOOLCHAIN_ONLY=<wbr>ON to your build,<br>
>>> >> though I'm not sure that should make any difference to the pdb files.<br>
>>> ><br>
>>> ><br>
>><br>
>><br>
><br>
</div></div></blockquote></div><br></div>