This message was posted on behalf of Intel Corporation
Thank you for contacting us.
We are aware of this issue, and I just want to let you know that we are working on this to fix it. We will contact you when we have updates.
We appreciate your patience.
The issue with the default manifest in pymavlink was fixed Fix the build break with pymavlink · intel-aero/intel-aero-manifest@69c1837 · GitHub
I've tested both manifests (default and dev) at Dashboard [Jenkins] and they succeed.
Thank you for fixing that.
We did a fresh compiling with the latest version in github. pymavlink and mavlink rounter passed compiling.
For pymavlink, the changes are the same with what we did.
For mavlink router, in the previous version if manifests, there was a patch file. The error was that the patch was for an old version of the Makefile.am and configure.ac. What we get from git are latest version of those two files, so patch file didn't match. We manually changed the patch file (mostly line numbers). It passed compiling with the previous version of manifests. In the latest version manifests, we can see now that the patch file got removed and changes were done in the .bb file, and the changes are different with the previous patch file. Not sure if it will get the same result as the patch. Hope it will. Anyway, doing a patch is a less preferred way. Thank you for removing that.
We still couldn't fetch the package "mesa-2_11.1.1", so had to manually download it and add the path of the local file in the .bb file.
I appreciate your input. pymavlink failed to download from upstream URL and that was fixed. The patch you refer is not needed anymore.
I checked the 'mesa-2_11.1.1" from aero-build-release #2 Console [Jenkins] and it shows no errors.
If you find problems with the recipe itself, please file an issue to Issues · intel-aero/meta-intel-aero · GitHub
Provide as much bitbake logging information as required to see the problem - please refer to Bitbake Cheat Sheet - eLinux.org for logging levels.