Hello, thank you for the prompt reply.
On Wed, Dec 16, 2015 at 09:05:19AM +0100, Hakan Ardo wrote:
> Thanks, this is fixed in unstable.
It is, but users of Debian testing right now receive confusing
messages and are not able to build anything. I might be
misunderstanding something but this seems
Package: avr-libc
Version: 1:1.8.0+Atmel3.4.5-1
Severity: grave
This current version depends on gcc-avr (>= 1:4.8.1+Atmel3.4.5), and
testing already ships 1:4.9.2+Atmel3.5.0-1 which formally fulfills the
dependency, however, the resulting combination is unusable as the
specs files supplied with gc
On Mon, Oct 20, 2014 at 03:43:43PM +0200, Luca Bruno wrote:
> On Monday 20 October 2014 17:31:48 Paul Fertser wrote:
> I see. So in the end, let's keep:
> * libusb autodetection for kfreebsd
> * --enable-usb_blaster_libftdi for linux
My proposal is to have libusb
On Mon, Oct 20, 2014 at 02:24:36PM +0100, Steven Chamberlain wrote:
> On 20/10/14 13:01, Paul Fertser wrote:
> > On Mon, Oct 20, 2014 at 01:45:15PM +0200, Luca Bruno wrote:
> >> I'm just slightly confused about usb-blaster on kfreebsd, which seems to
> >> have
&
On Mon, Oct 20, 2014 at 01:45:15PM +0200, Luca Bruno wrote:
> > MPSSE mode depends only on libusb-1, however, there're three other
> > drivers (USB Blaster, ASIX Presto, OpenJTAG; USB Blaster being really
> > important here) plus legacy ft2232 implementation that need
> > libftdi-dev.
>
> If I'm n
Hi,
On Sun, Oct 19, 2014 at 10:45:17PM +0100, Steven Chamberlain wrote:
> If you want something equivalent to Linux libusb 1.0 API, I think you
> need to Build-Depend on libusb2-dev [kfreebsd-any] rather than libusb-dev.
Right, libusb-0.1 API is still needed for some older drivers, but it
is prov
6 matches
Mail list logo
