On Thu, Jun 21, 2012 at 1:08 PM, Pete Batard <p...@akeo.ie> wrote:
> I'm gonna bump the priority of churning through the warnings, else I'm
> pretty sure they're going to fall through.
>
> Proposed patch attached. Please let me know if still get reports for the
> ones mentioned below.
>
All but the "statement is unreachable" are fixed.
>
> ..\libusb\os\windows_usb.c(**2124): warning #111: statement is
>> unreachable
>> usbi_dbg("ERROR: broken timer thread");
>>
>
> What statement? ;)
The patch is OK, but the compiler then throws the same warning on the next
line ("return 1;") so you need to remove the next line as well.
Orin.
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
libusbx-devel mailing list
libusbx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libusbx-devel
