Am 03.07.2012 08:49, schrieb Ludovic Rousseau:
> Why is the lib called libusb.a and not libusb-1.0.a?
>
> My hypothesis is that libusb.a comes from libusb-compat and is not
> (statically) linked with libusb (or libusbx). So of course all the
> libusb-1.0 symbols are missing.
> Can you check that?
C
2012/7/3 Tobias Powalowski :
> Am 03.07.2012 08:49, schrieb Ludovic Rousseau:
>> Why is the lib called libusb.a and not libusb-1.0.a?
>>
>> My hypothesis is that libusb.a comes from libusb-compat and is not
>> (statically) linked with libusb (or libusbx). So of course all the
>> libusb-1.0 symbols
Hi,
On 07/03/2012 12:43 AM, Pete Batard wrote:
> As per the roadmap. This is something I realized right after 1.0.12, as
> LOG_LEVEL_XYZ is lilely to be generic enoug to conflict with other apps and
> headers that may define those as well.
>
> This is also in part the source of Trac #31, which i
Am 03.07.2012 09:26, schrieb Ludovic Rousseau:
> 2012/7/3 Tobias Powalowski :
>> Am 03.07.2012 08:49, schrieb Ludovic Rousseau:
>>> Why is the lib called libusb.a and not libusb-1.0.a?
>>>
>>> My hypothesis is that libusb.a comes from libusb-compat and is not
>>> (statically) linked with libusb (or
Now libusb-compat errors with this during compile:
core.c:35:6: error: nested redefinition of 'enum usbi_log_level'
core.c:35:6: error: redeclaration of 'enum usbi_log_level'
In file included from core.c:27:0:
/usr/include/libusb-1.0/libusb.h:962:6: note: originally defined here
make[2]: *** [libus
On 2012.07.03 09:27, Tobias Powalowski wrote:
> Now libusb-compat errors with this during compile:
> core.c:35:6: error: nested redefinition of 'enum usbi_log_level'
> core.c:35:6: error: redeclaration of 'enum usbi_log_level'
> In file included from core.c:27:0:
This is a known issue.
Please app
On 2012.07.03 08:33, Hans de Goede wrote:
> Next time please send patches inline, that makes replying to them for a
> review a lot easier.
This is getting old.
The thing is, Segher complained once, so I went inline, then Xiaofan
complained about the extra '>' character, so I reverted back to non
v2, that applies Hans' suggestion.
NB: This patch should be attached as inline
Regards,
/Pete
>From 7ec94a45ed8155e7a1d4d5d75575099b09c78834 Mon Sep 17 00:00:00 2001
From: Pete Batard
Date: Mon, 2 Jul 2012 23:39:19 +0100
Subject: [PATCH] Core: Prefix LOG_LEVEL_ with LIBUSB_ to avoid conflict
On Mon, 2 Jul 2012 12:28:15 -0700
Sarah Sharp wrote:
> On Tue, Jun 26, 2012 at 01:16:46PM +0400, Igor Kuzmin wrote:
> > OK, so, with for-usb-linus kernel current results with different
> > controllers are:
> > NEC - works
> > Fresco Logic - fails with "ERROR Transfer event TRB DMA ptr not part of
On Tue, Jul 3, 2012 at 5:23 PM, Pete Batard wrote:
> On 2012.07.03 08:33, Hans de Goede wrote:
>> Next time please send patches inline, that makes replying to them for a
>> review a lot easier.
>
> This is getting old.
>
> The thing is, Segher complained once, so I went inline, then Xiaofan
> comp
On Tue, Jul 3, 2012 at 6:04 PM, Pete Batard wrote:
> v2, that applies Hans' suggestion.
>
> NB: This patch should be attached as inline
>
Actually it comes to me as both inline and attachment and both
are with the extra ">". Kind of strange, either something is wrong
with Gmail or something is wr
On 2012.07.03 13:59, Xiaofan Chen wrote:
>> NB: This patch should be attached as inline
>
> Actually it comes to me as both inline and attachment
Which is exactly what I want.
"Pure" inline is a PITA to work with, because everything's just text and
you never know if there's something of value in
On Tue, Jul 3, 2012 at 9:26 PM, Pete Batard wrote:
> On 2012.07.03 13:59, Xiaofan Chen wrote:
>>> NB: This patch should be attached as inline
>>
>> Actually it comes to me as both inline and attachment
>
> Which is exactly what I want.
I see. In that case, no problem.
> "Pure" inline is a PITA t
On Tue, 3 Jul 2012, Xiaofan Chen wrote:
> Actually what I complained is this one (extra ">" before "From"
> which is probably caused by the mailing list software.
> >From 7ec94a45ed8155e7a1d4d5d75575099b09c78834 Mon Sep 17 00:00:00 2001
Xiaofan, have you read "The UNIX-HATERS Handbook" by Garfink
Dear maintainer,
I encountered an issue using pcsc-lite and libusb on Ubuntu 10.04 LTS.
Now and then libusb segfaults and causes pcscd to crash.
The error occurred with libusb-1.0-0 (1.0.8), so I updated libusb-1.0-0 and
libusb-1.0-0-dev to 1.0.11 (libusbx) a few days ago, hoping the issue was f
Hi Sebastian,
On 2012.07.03 15:35, sebasti...@gmx-topmail.de wrote:
> I encountered an issue using pcsc-lite and libusb on Ubuntu 10.04 LTS.
> Now and then libusb segfaults and causes pcscd to crash.
>
> The error occurred with libusb-1.0-0 (1.0.8), so I updated libusb-1.0-0 and
> libusb-1.0-0-de
2012/7/3 :
> Dear maintainer,
Hello,
> I encountered an issue using pcsc-lite and libusb on Ubuntu 10.04 LTS.
> Now and then libusb segfaults and causes pcscd to crash.
>
> The error occurred with libusb-1.0-0 (1.0.8), so I updated libusb-1.0-0 and
> libusb-1.0-0-dev to 1.0.11 (libusbx) a few d
2012/7/3 Pete Batard :
> Provided pcscd will log stderr output from libusbx, that the volume of
> USB traffic is not too prohibitive, and that you can be alerted and act
> on a crash in a matter of hours, here's what I would do:
> * using the 1.0.12 libusbx source tarball, configure libusbx with
>
On 2012.07.03 14:38, Xiaofan Chen wrote:
> I sent the patch both inline and as an attachment using Gmail.
> Both are okay from what I see, no extra ">". But maybe you
> will see the ">" for the inline version. Did you see the ">" for
> my attachment?
Yup. This is how Thunderbird displays the inlin
First of all, I’d like to thank you both very much for your fast response.
I use pcsc in a productive environment (24/7), where contactless smardcards are
used to grant access to an application. Because there are more than 25
pc-terminals involved, I’d appreciate a non disturbing and simple way
20 matches
Mail list logo
