[OE-core] [PATCH 1/1] Update libusb1 from 1.0.19 to 1.0.20

[Burton, Ross]

On 8 October 2015 at 15:36, Jens Rehsack <rehsack at gmail.com> wrote:

> This updates libusb1 from 1.0.19 to 1.0.20
>
> 2015-09-13: v1.0.20
> * Add Haiku support
> * Fix multiple memory and resource leaks (#16, #52, #76, #81)
> * Fix possible deadlock when executing transfer callback
> * New libusb_free_pollfds() API
> * Darwin: Fix devices not being detected on OS X 10.8 (#48)
> * Linux: Allow larger isochronous transfer submission (#23)
> * Windows: Fix broken builds Cygwin/MinGW builds and compiler warnings
> * Windows: Fix broken bus number lookup
> * Windows: Improve submission of control requests for composite devices
> * Examples: Add two-stage load support to fxload (#12)
> * Correctly report cancellations due to timeouts
> * Improve efficiency of event handling
> * Improve speed of transfer submission in multi-threaded environments
> * Various other bug fixes and improvements
> The (#xx) numbers are libusb issue numbers, see ie:
> https://github.com/libusb/libusb/issues/16
>

And apparently introduces a parallel make race :(

mv: cannot stat `libusb_1_0_la-sync.loT': No such file or directory
mv: cannot stat `libusb_1_0_la-descriptor.loT': No such file or directory
mv: cannot stat `libusb_1_0_la-core.loT': No such file or directory
mv: cannot stat `libusb_1_0_la-hotplug.loT': No such file or directory
mv: cannot stat `libusb_1_0_la-io.loT': No such file or directory
i686-poky-linux-libtool:   error: 'os/libusb_1_0_la-linux_usbfs.lo' is not
a valid libtool object
make[3]: *** [libusb-1.0.la] Error 1
make[3]: Leaving directory
`/home/pokybuild/yocto-autobuilder/yocto-worker/ptest-x86/build/build/tmp/work/core2-32-poky-linux/libusb1/1.0.20-r0/build/libusb'
make[2]: *** [all-recursive] Error 1

(full log at http://errors.yoctoproject.org/Errors/Details/21443/)

Ross
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20151106/f1918a2c/attachment-0002.html>