Displaying 4 results from an estimated 4 matches for "d_consol".
Did you mean:
d_console
2015 Jul 24
2
[LLVMdev] [lldb-dev] [3.7 Release] We have branched
...ailed, but I think the error message was
>>> different, so this could be a regression bug but hopefully it's actually an
>>> improvement. Current error message:
>>>
>>> cl -c -I. -nologo -GF -W3 -I..\lib\CORE -I.\include -I. -I..
>>> -DWIN32 -D_CONSOLE -DNO_STRICT -DWIN64 -DCONSERVATIVE
>>> -D_CRT_SECURE_NO_DEPRECATE -D_CRT_NONSTDC_NO_DEPRECATE -DPERLDLL -DPERL_CORE
>>> -O1 -MD -Zi -DNDEBUG -GL -fp:precise -DPERL_TEXTMODE_SCRIPTS
>>> -DPERL_IMPLICIT_CONTEXT -DPERL_IMPLICIT_SYS -TP -EHsc -Foperllib.obj
>>> p...
2015 Jul 16
2
[LLVMdev] [lldb-dev] [3.7 Release] We have branched
...>
> Build Perl - fails. 3.6 also failed, but I think the error message was
> different, so this could be a regression bug but hopefully it's actually an
> improvement. Current error message:
>
> cl -c -I. -nologo -GF -W3 -I..\lib\CORE -I.\include -I. -I..
> -DWIN32 -D_CONSOLE -DNO_STRICT -DWIN64 -DCONSERVATIVE
> -D_CRT_SECURE_NO_DEPRECATE -D_CRT_NONSTDC_NO_DEPRECATE -DPERLDLL -DPERL_CORE
> -O1 -MD -Zi -DNDEBUG -GL -fp:precise -DPERL_TEXTMODE_SCRIPTS
> -DPERL_IMPLICIT_CONTEXT -DPERL_IMPLICIT_SYS -TP -EHsc -Foperllib.obj
> perllib.c
> clang-cl.exe: warn...
2015 Jul 24
0
[LLVMdev] [lldb-dev] [3.7 Release] We have branched
...- fails. 3.6 also failed, but I think the error message was
>> different, so this could be a regression bug but hopefully it's actually an
>> improvement. Current error message:
>>
>> cl -c -I. -nologo -GF -W3 -I..\lib\CORE -I.\include -I. -I..
>> -DWIN32 -D_CONSOLE -DNO_STRICT -DWIN64 -DCONSERVATIVE
>> -D_CRT_SECURE_NO_DEPRECATE -D_CRT_NONSTDC_NO_DEPRECATE -DPERLDLL -DPERL_CORE
>> -O1 -MD -Zi -DNDEBUG -GL -fp:precise -DPERL_TEXTMODE_SCRIPTS
>> -DPERL_IMPLICIT_CONTEXT -DPERL_IMPLICIT_SYS -TP -EHsc -Foperllib.obj
>> perllib.c
>>...
2015 Jul 15
10
[LLVMdev] [3.7 Release] We have branched
Hi all,
The 3.7 release branch was created from trunk at r242221 today (around
10:40 pm UTC).
Branch policy:
- Any doc changes can go in. Updates to the release notes are highly
encouraged, and should be committed directly to the branch.
- All other patches should be approved by the release manager (me) and
the appropriate code owner. To get a change merged, commit it to
trunk, and then reply