Just wondering if this could be fixed. Potential fix: http://git.libusb.org/?p=libusb-pbatard.git;a=commit;h=5f950c84feff96c942ec63bd3b0041f944e8fefc;js=1
Regards, Xiaofan ---------- Forwarded message ---------- From: Pete Batard <[email protected]> Date: Mon, Sep 19, 2011 at 3:06 AM Subject: Re: [Libusb-devel] libusb-1.0.9-rc1 pushed, libusb.git/testing, what now? To: [email protected] On 2011.09.18 15:33, Xiaofan Chen wrote: > There are two minor warnings for MinGW-w64 4.6.2 gcc. > > CC libusb_1_0_la-io.lo > ../../libusb/io.c: In function 'get_next_timeout': > ../../libusb/io.c:1961:3: warning: suggest parentheses around '&&' > within '||' [-Wparentheses] > ../../libusb/io.c: In function 'libusb_get_next_timeout': > ../../libusb/io.c:2265:2: warning: suggest parentheses around '&&' > within '||' [-Wparentheses] These have always been there. At least, I've always gotten those with MinGW-w64 in -pbatard until I applied [1]. This is a pure MinGW issue (their timercmp should be defined better). If anybody wants to mention it to them (again, AFAIK), be my guest. Regards, /Pete [1] http://git.libusb.org/?p=libusb-pbatard.git;a=commit;h=5f950c84feff96c942ec63bd3b0041f944e8fefc;js=1 ------------------------------------------------------------------------------ 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
