I went one step further and tied building it on the 410c anyways. I figured that we don’t need to cross compile, so we don’t need the mulitlibs so it should just build. I ran the apt-get with all of the other packages except gcc-multilibs. Unfortunately once you get to the bitbake step you get an error:
ERROR: Uninative selected but not configured correctly, please set UNINATIVE_CHECKSUM[aarch64]
The bitbake system seems to check checksums on everything and decides that it has never been tested and validated on an aarch64 system so it refuses to even try building AGL.
Next I went to an almost Ubuntu system, I tried to do the bitbake on Ubuntu under WSL (Windows Subsystem for Linux) which is an x86_64 system usually works for most things, but bitbake fails on this system also, with many error messages, but most importantly this one:
pyinotify.WatchManagerError: add_watch: cannot watch /home/ljking/workspace/workspace_agl/build/conf WD=-1, Errno=Invalid argument (EINVAL)
it appears that bitbake is trying to use a Linux feature that is not implemented in WSL.
Finally I trued it on a real Linux box, and the bitbake works exactly as expected. It hasn’t finished compiling yet, so I haven’t tested the final image, but I expect it will work just fiine.
@danielt it appears we have two issues here, both not really specific to the DragonBoard
- gcc-multilib should be available in the aarch64 Debian packages but isn’t
- bitbake needs to learn that it can run on a aarch64 host.
Full Disclosure: I am an employee of Qualcomm Canada, any opinions I may have expressed in this or any other post may not reflect the opinions of my employer.