embedded libftdi dependency seems broken |
||
Issue descriptionI am not sure how this works on the builders, but in my setup I can't emerge chromeos-ec for any of the boards I tried. samus is a typical example: running emerge-samus chromeos-ec fails because libftdi (a chromeos-ec dependency) is failing to emerge, as it is missing boost. Boost is a dependency in src/third_party/chromiumos-overlay/dev-embedded/libftdi/libftdi-1.0.ebuild but only in case the 'cxx' USE flag is set, which is not for the embedded targets it looks like. Manually emerging boost for the target fixes the problem, but I am not sure what is a better fix for the libftdi ebuild - making boost an unconditional dependency maybe?
,
Mar 17 2016
this seems odd - have we ever modified libftdi? It seems to have legit use cases of boost. What happened anyway, why did this start failing, it must have worked earlier. Unless my situation is different such that I build only firmware, not the rest of the packages, those could be pulling boost in.
,
Mar 17 2017
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
||
►
Sign in to add a comment |
||
Comment 1 by vapier@chromium.org
, Mar 17 2016