On 2011.09.21 07:51, Ozkan Sezer wrote:
> Hmm, do the following fix your case?
>
> Kai?
>
> --- _timeval.h~       2010-05-26 20:21:09.000000000 +0300
> +++ _timeval.h        2011-09-21 09:48:42.000000000 +0300
> @@ -16,7 +16,7 @@ struct timeval
>   #define timerisset(tvp)             ((tvp)->tv_sec || (tvp)->tv_usec)
>   #define timercmp(tvp,uvp,cmp)                                       \
>               ((tvp)->tv_sec cmp (uvp)->tv_sec ||             \
> -              (tvp)->tv_sec == (uvp)->tv_sec&&  (tvp)->tv_usec cmp 
> (uvp)->tv_usec)
> +              ((tvp)->tv_sec == (uvp)->tv_sec&&  (tvp)->tv_usec cmp 
> (uvp)->tv_usec))
>   #define timerclear(tvp)             (tvp)->tv_sec = (tvp)->tv_usec = 0
>
>   #endif /* _TIMEVAL_DEFINED */

Hi Kai,

Yes it does. Thanks for looking into it.

/Pete

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________
Mingw-w64-public mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Reply via email to