[yocto] Errors building with Windows Subsystem for Linux (aka Bash on Ubuntu on Windows)
Burton, Ross
ross.burton at intel.com
Tue Sep 26 15:15:17 PDT 2017
On 26 September 2017 at 22:01, Bryan Evenson <bevenson at melinkcorp.com>
wrote:
> Now this *is* interesting. Try removing the repeated slashes just in case
> the WSL ln is being incredibly pedantic (ie sstate-build-package//packages-split),
> but I don't seriously expect that to be the problem. Running stat on the
> source and verifying the destination doesn't exist would be helpful. Can
> you tell if that is the first ln that it is trying to do, or do many work
> and that one fails? Does WSL have a working strace or similar to identify
> which exact syscall is failing?
>
>
>
> I am about 60% through the full image build when it gets to glibc-locale
> with about half of the packages for the image fully complete. I did a stat
> on one of the source files and verified it did exist, and it had 0644 for
> access rights and is owned by me. I also verified that the destination
> file doesn’t exist. WSL does have a working strace. I ran strace on the
> failed cp command shown above and I now have a 56MB strace output file.
> What should I be looking for in this file?
>
Feel free to compress and email it directly to me, but simply grepping for
EINVAL (invalid argument error) might be enough.
Ross
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20170926/04df0add/attachment.html>
More information about the yocto
mailing list