[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Lzip-bug] mingw build failure

From: Antonio Diaz Diaz
Subject: Re: [Lzip-bug] mingw build failure
Date: Thu, 10 Jan 2013 20:16:15 +0100
User-agent: Mozilla/5.0 (X11; U; Linux i586; en-US; rv:1.7.11) Gecko/20050905

Hello Roy,

Roy wrote:
There is no _fsetmode() in mingw environment.

I knew I chose the wrong one. I'll switch again to setmode[1]. ;-)

[1] http://lists.nongnu.org/archive/html/lzip-bug/2010-08/msg00011.html

BTW, I have been told that cygwin now uses binary IO only[2]. Someone knows if mingw plans to do the same?

[2] http://lists.nongnu.org/archive/html/lzip-bug/2010-08/msg00005.html

BTW it will be nice to #define strtoll as _strtoi64, as older w32api versions will not have this defined.

#define strtoll _strtoi64

Is there any condition that can be reliably tested to apply this definition?

for clzip, does unistd.h is really needed? In TinyCC win32 environment, it doesn't have it. I commented they out and it builds with tcc(although the result binary is slow).

Yes, it is. At least in GNU/Linux. And I don't think it is worth the trouble of including it conditionally just for the sake of tcc.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]