On 20/09/2019 13:22, Mittal, Anuj wrote:
On Fri, 2019-09-20 at 11:33 +0100, Ross Burton wrote:
On 20/09/2019 02:16, Mittal, Anuj wrote:
On Thu, 2019-09-19 at 23:55 +0100, Ross Burton wrote:
The git-lfs content is only used by the samples which we don't
use or
install. Set lfs=0 so that git-lfs isn't a requirement on the
build
host.
It still tries to fetch the content at the time of unpacking. This
is
what I get during do_unpack when git-lfs in not in HOSTTOOLS:
git -c core.fsyncobjectfiles=0 checkout -B intel-mediasdk-19.2
885c309f57a7a1cbc60edee6b0d014a36da94562 failed with exit code 128,
output:
git-lfs filter-process: git-lfs: command not found
fatal: the remote end hung up unexpectedly
I forgot to put in the commit message:
This needs the lfs option to the git fetcher, which is currently
in
bitbake master as of be0b78ccfc5ede98041bc0545a15092494b12b26.
Yes, I have that commit in my tree. Only change is I commented
HOSTTOOLS_NONFATAL = git-lfs in bitbake.conf and manually removed git-
lfs link from tmp/hosttools.
What happens if you actually remove git-lfs from the host, instead of
fiddling HOSTTOOLS? I'm wondering if this is git looking for git-lfs in
/usr/bin explicitly, but then trying to run it with PATH lookup which
fails as /usr/bin isn't in $PATH.
Ross
--
_______________________________________________
meta-intel mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/meta-intel
