Displaying 3 results from an estimated 3 matches for "statusunsupported".
2014 Sep 17
4
[LLVMdev] proposal to avoid zlib dependency.
...<bob.wilson at apple.com> wrote:
> If you build with configure+make, just run configure with —disable-zlib.
> We do this routinely, so I’m pretty sure it works.
>
It "works" as in it builds. However, the support for it is disabled since
zlib::compress will always return StatusUnsupported, so the debug
information will just not be compressed. Effectively, compressed DWARF is
unsupported on Windows.
> On Sep 16, 2014, at 3:42 PM, Reid Kleckner <rnk at google.com> wrote:
>
> It might not be available, so all codepaths have to recover from zlib
> unavailability. Fo...
2014 Sep 16
2
[LLVMdev] proposal to avoid zlib dependency.
It might not be available, so all codepaths have to recover from zlib
unavailability. For example, I don't think compressed DWARF works on
Windows.
On Tue, Sep 16, 2014 at 3:21 PM, Filip Pizlo <fpizlo at apple.com> wrote:
> What is the downside of Zlib dependency? I'm curious! :-)
>
> -Filip
>
> On Sep 16, 2014, at 2:45 PM, Christophe Duvernois <
>
2014 Sep 18
2
[LLVMdev] proposal to avoid zlib dependency.
...f you build with configure+make, just run configure with --disable-zlib.
>>> We do this routinely, so I'm pretty sure it works.
>>>
>>
>> It "works" as in it builds. However, the support for it is disabled
>> since zlib::compress will always return StatusUnsupported, so the debug
>> information will just not be compressed. Effectively, compressed DWARF is
>> unsupported on Windows.
>>
>>
>>> On Sep 16, 2014, at 3:42 PM, Reid Kleckner <rnk at google.com> wrote:
>>>
>>> It might not be available, so all c...