On 1/13/2013 11:27, Roy Tam wrote:
> 2013/1/13 Antonio Diaz Diaz <[email protected]>:
>> Roy Tam wrote:
>>>
>>> actually it is safe to #define it to _strtoi64 in mingw as _strtoi64
>>> is always exists in MSVCRT.
>>
>>
>> I hope you are right because I have just released lzip-1.14-rc2 with
>> strtoull defined to _strtoi64. BTW, this version uses strtoull instead of
>> strtoll, but I guess _strtoi64 may be fine because the maximum valid  value
>> is in the range of a signed long long.
> 
> for strtoull in mingw, use _strtoui64. (
> http://msdn.microsoft.com/en-US/library/85zk715d%28v=vs.80%29.aspx )
> for document about _strtoi64, it isavailable here:
> http://msdn.microsoft.com/en-US/library/h80404d3%28v=vs.80%29.aspx
> but g++ complains there is no header about it, I think keep using
> strtoll/strtoull in C++ version will be better.
> (the function exists in MSVCRT.dll but mingw header does not have prototypes)

mingw-w64 builds 64bit lzip fine, make check reports all pass.

It should be noted that that not all mingw are equal. So, please avoid
using __MINGW32__ to select features.



Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
Lzip-bug mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/lzip-bug

Reply via email to