X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:date:message-id:subject:from:to
	:content-type; q=dns; s=default; b=i8i6kcRYhCwZOU+R+BUe6hje+g6mG
	i0acixoDVrz2DrAJWVRS5uhlZhtflv+MwZbDZnz5MbZg7hJwXA5PhBkf26RtC5kU
	E+CION5WqSCio2Up66PAWmLW+BAG6vyDxmwW13HWrBqf7tanaacM46fLmTqgwRH2
	LV0kMsbdj68uMQ=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:date:message-id:subject:from:to
	:content-type; s=default; bh=48kjUknI8mQOsdRsPrGLVyFz5Hs=; b=X3x
	VMASWa6fGV4rVXfuYFhi5JYYrE3Ocvb/i4b5JvmccFksMY0BzESi3PDBAELq3DMc
	qoGS8JKoNY2csBF8jgDB5VnXcCv+8SED+WrpY624idqVoIB985XwwUz0wJfFShTN
	xMkAXylfwdbRcis0EUmwJiIVCvZL3G4b9OAxF+Gw=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2
X-HELO: mail-oi0-f43.google.com
MIME-Version: 1.0
X-Received: by 10.202.68.8 with SMTP id r8mr14372oia.116.1446621906349; Tue, 03 Nov 2015 23:25:06 -0800 (PST)
Date: Wed, 4 Nov 2015 16:25:06 +0900
Message-ID: <CAPYQg325xo_y2qO_Pc3ks-H6RicQK7w=oisW1mTiEt1zPwv9EQ@mail.gmail.com>
Subject: bump libusb packages?
From: KIMURA Masaru <hiyuh DOT root AT gmail DOT com>
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=UTF-8
X-IsSubscribed: yes

Hi,

can someone bump libusb packages to v1.0.20 or HEAD?
FYI, v1.0.20 and HEAD have a compilation issue[1],
was already reported to the upstream, but is not fixed ATM.

Peace,
-----
[1] https://github.com/libusb/libusb/issues/104
-----
$ cygcheck -c -d libusb1.0 libusb1.0-devel
Cygwin Package Information
Package              Version
libusb1.0            1.0.19-1
libusb1.0-devel      1.0.19-1

$ cd ~/git-repos
$ git clone https://github.com/libusb/libusb.git
$ cd libusb
$ git log v1.0.19... | grep -e 'Windows:'
    Windows: Fix potential memory leak
    Windows: Regenerate libusb-1.0.def file from latest DLL
    Windows: Fix some build warnings/link issues
    Windows: Close HID handles when closing composite devices
    Windows: Remove redundant check in windows_claim_interface()
    Windows: Destroy autoclaim_lock during cleanup
    Windows: Check for "calloc" allocation failure.
    Windows: Remove erroneous call to CloseHandle and add comments
    Windows: Improve monotonic clock_gettime() implementation
    Windows: Fix wIndex in setup packet for config descriptor request
    Windows: Fix broken build caused by missing rename in 63a440f1
    Windows: Free all WinUSB handles when closing a device
    Windows: Direct control requests to a specific interface when possible
    Windows: fix 2 bugs in windows_handle_events()
    Windows: Silence VS2013 code analysis warnings
    Windows: Fix cygwin64 build
    Windows: Define WINVER to fix building on MinGW

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple