On 02/01/2018 01:36 PM, Mauno Niko wrote:
Before we can declare that, we need to look what comm is actually used
for during build, and why its absence is not a problem and doesn't cause
errors.
Consider also that using comm from host may break reproducibility, if
absence or presence of comm on the host results in a different output
from the build.
My patch initially did add coreutils-native to u-boot DEPENDS.
Should I resubmit it? (did not apply due to mismatch in recipe filename
(version))
RP has already merged the patch you sent, I think :)
Still, in my opinion - yes, it's better to undo the HOSTTOOLS change,
and add coreutils-native. But first, research a bit further for what
purpose comm is used during build and why its absence doesn't break it.
Alex
--
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
