As promised. Hopefully this will silence the warnings raised by Clang on
OS-X.
And again, if someone wants to look into silencing that -std=gnu99 one,
you're welcome to submit a patch. I'm not planning to look into it, but
that doesn't mean there won't be review+integration of a patch if one i
On 2012.06.28 14:14, Xiaofan Chen wrote:
> Enclosed please also find the zip of the html files.
Thanks! That helps a bit.
The two warnings in core are false positives that I think can be fixed
easily by having the following at line 686:
struct libusb_device **devs = NULL;
If you have a chance,
Hi Rich,
On 2012.06.28 15:00, Xiaofan Chen wrote:
> On Tue, Jun 26, 2012 at 4:52 AM, Rich von Lehe wrote:
>> In lieu of set_configuration in this case (there is only one config),
>> one process would claim_interface 0 and the other process would
>> claim_interface 1. I have a suspicion that the
On Thu, 28 Jun 2012 22:09:06 +0800, Xiaofan Chen said:
>You are right. The error message is misleading and indeed the
>linking invocation causes this message.
And indeed, when linking already-compiled object files, why would the linker
care what dialect of C was used in the source files?
But it
On Thu, Jun 28, 2012 at 9:36 PM, Sean McBride wrote:
> On Wed, 27 Jun 2012 20:39:52 +0200, Ludovic Rousseau said:
>>> We're specifying gnu99 in AM_CFLAGS, so I wouldn't expect it to end up
>>> in LD_FLAGS. This is benign, so I'm not sure it's worth spending time on
>>> fixing that.
>>
>>clang is c
On Tue, Jun 26, 2012 at 4:52 AM, Rich von Lehe wrote:
> In lieu of set_configuration in this case (there is only one config),
> one process would claim_interface 0 and the other process would
> claim_interface 1. I have a suspicion that the underlying
> implementation in Libusb is locking the dev
On Wed, 27 Jun 2012 20:39:52 +0200, Ludovic Rousseau said:
clang: warning: argument unused during compilation: '-std=gnu99'
>>>
>>> The warning you see is telling you that you are specifying -std=gnu99
>when linking, which does nothing. gcc silently ignores that flag when
>linking, I believe
On 2012.06.28 04:19, Jach Fong wrote:
> On 27 Jun 2012 15:12:39 Pete Batard wrote:
>>
>> According to the error returned (LIBUSB_ERROR_NOT_FOUND) that seems to
>> be the case. This is the error the Windows backend returns if it was
>> unable to cache a config descriptor durin enum.
>>
>> Jach, if
