Closed brunosmmm closed 6 years ago
Saw this now, I think Xen tree got overwritten somehow which is unfortunate. You can set BRANCH = "" as workaround (BRANCH_pn-xen = "" in local.conf) This will ensure nobranch=1 is used and will search the entire tree
When trying to build (using Yocto distribution fetched using github.com/Xilinx/yocto-manifests), 2017.4 building xen fails with:
Upon further inspection, the commit 75c00aca503fe7093ccfecb3d0dd803642cb7bae does not belong to any branch in the tree. It is tagged as rel-v2017.4 which makes sense as to why this revision would be selected in the rel-v2017.4 branch of meta-petalinux. (I am avoiding 2018.1 for now)
Temporarily fixed it by using the latest commit in the upstream branch, however this is pretty annoying.