Hi Arno, > -----Original Message----- > From: [email protected] [mailto:meta-xilinx- > [email protected]] On Behalf Of Arno Steffens > Sent: Friday, July 27, 2018 12:59 AM > To: meta xilinx <[email protected]> > Subject: [meta-xilinx] Nothing PROVIDES 'virtual/xilinx-platform-init' > > Hello, > After upgrade to Sumo I found some errors, that I can't understand. > As fas as I can see the microzed_zynq7 is still available? > > ERROR: Nothing PROVIDES 'virtual/xilinx-platform-init' (but > /home/user/y/yocto25/poky/meta/recipes-bsp/u-boot/u-boot_2018.01.bb > DEPENDS on or otherwise requires it) > zybo-linux-bd PROVIDES virtual/xilinx-platform-init but was skipped: > incompatible > with machine microzed-zynq7 (not in COMPATIBLE_MACHINE) > platform-init PROVIDES virtual/xilinx-platform-init but was skipped: > incompatible > with machine microzed-zynq7 (not in COMPATIBLE_MACHINE) > ERROR: Required build target 'virtual/boot-bin' has no buildable providers. > Missing or unbuildable dependency chain was: ['virtual/boot-bin', > 'virtual/xilinx- > platform-init'] > > I checked u-boot_2018.01.bb, it included u-boot-common_2018.01.inc, but I > can't > see a requirement for vitural/xilinx-platform-init? > > And also I found "microzed-zynq7" is still in meta-xilinx, as for instance: > ./meta-xilinx-bsp/recipes-bsp/device-tree/device- > tree.bbappend:COMPATIBLE_MACHINE_microzed-zynq7 = ".*" > > So what happened here? > > As background: > I created my own layer and set in > meta-my/conf/local.conf.sample > # This sets the default machine to be qemux86 if no other machine is selected: > MACHINE ??= "microzed-zynq7" > > Than I call > TEMPLATECONF=~/sdd/yocto25/meta-my/conf/ source ~/sdd/yocto25/poky/oe- > init-build-env ~/sdd/yocto25/my >
There is an issue on meta-xilinx-contrib recipe causing the issue. I have sent out a patch to fix this Thanks, Manju -- _______________________________________________ meta-xilinx mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-xilinx
