The official snapshots and releases still only include the toolchain,
by passing -DLLVM_INSTALL_TOOLCHAIN_ONLY=ON.
On Tue, Feb 20, 2018 at 4:54 PM, Reid Kleckner wrote:
> I didn't think we included the .lib files in the NSIS package. Do we do that
> now? I know users asked for it, but I thought w
I'm guessing this is a problem with NSIS failing to handle large files
though, and I'm not sure there's much we can do about it.
On Mon, Feb 19, 2018 at 10:54 PM, masaru tsuchiyama wrote:
> But it failed with -DLLVM_ENABLE_PDB=ON option .
>
> The error message is
> File: "lldELF.lib"
> Internal c
Ah, great.
Reid, seems like you fixed this user's issue.
On Mon, Feb 19, 2018 at 1:45 PM, masaru tsuchiyama wrote:
> It seems the change of the commit was disabled by default at r325296.
>
> Regards.
>
>
> 2018-02-19 19:55 GMT+09:00 Hans Wennborg :
>>
>> No, I didn't change anything here and I d
It seems the change of the commit was disabled by default at r325296.
Regards.
2018-02-19 19:55 GMT+09:00 Hans Wennborg :
> No, I didn't change anything here and I don't think Zach did either.
>
> On Sun, Feb 18, 2018 at 9:39 AM, masaru tsuchiyama
> wrote:
> > It didn't happen at r325456.
> >
No, I didn't change anything here and I don't think Zach did either.
On Sun, Feb 18, 2018 at 9:39 AM, masaru tsuchiyama wrote:
> It didn't happen at r325456.
> Did you fix it?
>
> Regards.
>
> 2018-02-17 5:57 GMT+09:00 masaru tsuchiyama :
>>
>> > Is that a solution to your problem?
>>
>> No.
>>
It didn't happen at r325456.
Did you fix it?
Regards.
2018-02-17 5:57 GMT+09:00 masaru tsuchiyama :
> > Is that a solution to your problem?
>
> No.
> It could be a workaround, but not a solution.
> I think we need to know the reason why the commit and the option affect
> the result at least.
>
> Is that a solution to your problem?
No.
It could be a workaround, but not a solution.
I think we need to know the reason why the commit and the option affect
the result at least.
2018-02-16 19:05 GMT+09:00 Hans Wennborg :
> On Thu, Feb 15, 2018 at 11:43 PM, masaru tsuchiyama
> wrote:
> > H
On Thu, Feb 15, 2018 at 11:43 PM, masaru tsuchiyama wrote:
> Hi,
>
>> Is there any info about what went wrong in NSISOutput.log?
>
> I attach the log.
>
> This is the last part of the log.
>
> File: "clangStaticAnalyzerCheckers.lib"
>
> Internal compiler error #12345: error mmapping file (210
+Zach for r324504
On Tue, Feb 13, 2018 at 1:45 PM, masaru tsuchiyama via cfe-users
wrote:
> Hello
>
> llvm build fails at r324504 or later.
> I used the attached file to build. (renamed to .txt)
>
> example:
>clang-build.bat ninja x86 update 324806
>
> This is the tail of the failure log.
>
Hello
llvm build fails at r324504 or later.
I used the attached file to build. (renamed to .txt)
example:
clang-build.bat ninja x86 update 324806
This is the tail of the failure log.
CPack: Create package using NSIS
CPack: Install projects
CPack: - Install project: LLVM
Creating llvm-ranlib
10 matches
Mail list logo
