hdctools - toad build fails due to missing dependency
Reported by
emcginni...@gmail.com,
Feb 27 2017
|
|||
Issue descriptionChromeOS version hdcTools git https://chromium.googlesource.com/chromiumos/third_party/hdctools/+/d475e625989bc150461372466cd4b5099a10b206 Steps to reproduce the problem: 1. Clone hdctools on a system with gcc 4.9 to 5.4.1 (e.g. Debian jessie/yakkety) 2. 'make' What is the expected behavior? Build does not fail What went wrong? Build fails Finished prerequisites of target file 'toad'. Must remake target 'toad'. Putting child 0x55e24d3f3560 (toad) PID 6838 on the chain. Live child 0x55e24d3f3560 (toad) PID 6838 [2] Linking toad /usr/bin/ld: toad.o: undefined reference to symbol 'usb_get_descriptor' //lib/x86_64-linux-gnu/libusb-0.1.so.4: error adding symbols: DSO missing from command line collect2: error: ld returned 1 exit status Reaping losing child 0x55e24d3f3560 PID 6838 /home/user/hdctools/src/toad/Makefile:27: recipe for target 'toad' failed make[2]: *** [toad] Error 1 Removing child 0x55e24d3f3560 PID 6838 from chain. Reaping losing child 0x55ae80c8a680 PID 6830 /home/user/hdctools/src/Makefile:13: recipe for target 'toad' failed make[1]: *** [toad] Error 2 Removing child 0x55ae80c8a680 PID 6830 from chain. Reaping losing child 0x5610e10d8da0 PID 6822 Makefile:21: recipe for target 'src' failed make: *** [src] Error 2 Removing child 0x5610e10d8da0 PID 6822 from chain. Did this work before? N/A this is related to a previously addressed bug: https://bugs.chromium.org/p/chromium/issues/detail?id=465535# One of the comments on the previous report suggest installing libusb-1.0, this does not fix the issue as it seems to by default use libusb-0.1 I've remade the diff file from the previous report to apply to the most recent revision at the time of posting
,
Nov 3 2017
modia@, did you accidentally set the wrong component?
,
Nov 3 2017
building hdctools on debian isn't something we support AFAIK. Please take a look at the chroot in the developer guide for a consistent build environment. This bug was sorted as part of the test team's effort to classify issues without a component. For hdctools, I suspect OS>Firmware is a reasonable component. |
|||
►
Sign in to add a comment |
|||
Comment 1 by modia@chromium.org
, Nov 3 2017