Re: Errors building with Windows Subsystem for Linux (aka Bash on Ubuntu on Windows)
From: Burton, Ross [mailto:ross.burton@...]
Sent: Tuesday, September 26, 2017 3:13 PM
To: Bryan Evenson <bevenson@...>
Subject: Re: [yocto] Errors building with Windows Subsystem for Linux (aka Bash on Ubuntu on Windows)
On 26 September 2017 at 18:16, Bryan Evenson <bevenson@...> wrote:
That's the buildstats class that is enabled in your local.conf. I don't expect WSL will ever fake a Linux-compatible /proc directory structure, so you can just disable this.
OK. I removed that from my local.conf and the warning went away.
This is just standard curses, so you'll have to wait for Microsoft to make it faster.
If you do "bitbake <your targets> | cat" then bitbake will fall back to a UI that isn't interactive and will be a lot faster.
After I disabled buildstats, the refresh noticeably improved. From looking at buildstats.bbclass, I see a number of ‘stat’ calls. I’m guessing the stat call has some efficiency improvements left to go on WSL.
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?
In all honestly I'm surprised you got the build to go as far as you have under WSL, that's impressive. Have you been able to compare performance against a full VM on the same hardware?
I haven’t got far enough to do a good performance comparison. Overall performance seems similar, maybe a little slower than against a full VM.