Hi Peter, From: [email protected] [mailto:[email protected]] Sent: Tuesday, December 27, 2016 11:35 AM To: Manjukumar Harthikote Matha; [email protected] Subject: RE: [meta-xilinx] Failure building Docker with Yocto 2016.4
Hi Manju, >I have replicated the problem Mani E reported over on the other mailing list >using the flow detailed here http://www.wiki.xilinx.com/Yocto+OSL+Image+build >with the rel-v2016.4 branch name, so to answer your question regarding the >toolchain, yes it’s >using the Xilinx toolchain. >I am building in a Ubuntu 14.04 container I have been using successfully for >the last few weeks. I can try with a similarly configured Ubuntu 16.04 >container if you want? >What’s interesting is that the error does not occur when I build with the >following bblayers.conf after cloning the necessary repo’s from Yocto and Open >Emebdded and doing a “git checkout krogoth” in all the non Xilinx repo’s and a >“git checkout rel-?>v2016.4” in the meta-xilinx repo. I found an issue with https://github.com/Xilinx/meta-petalinux/blob/rel-v2016.4/classes/go-osarchmap.bbclass Can you remove this and build. We don’t test for go package hence did not see this issue earlier. I will rework the above bbclass and send a patch. Thanks Manju > I built with “MACHINE=qemuzynqmp bitbake go-cross” in both cases after adding > IMAGE_INSTALL_append = “ docker” to my local.conf. # POKY_BBLAYERS_CONF_VERSION is increased each time build/conf/bblayers.conf # changes incompatibly POKY_BBLAYERS_CONF_VERSION = "2" BBPATH = "${TOPDIR}" BBFILES ?= "" BBLAYERS ?= " \ /data/poky/meta \ /data/poky/meta-poky \ /data/poky/meta-yocto-bsp \ /data/meta-xilinx \ /data/meta-openembedded/meta-oe \ /data/meta-openembedded/meta-networking \ /data/meta-openembedded/meta-filesystems \ /data/meta-openembedded/meta-python \ /data/meta-virtualization \ /data/openembedded-core/meta \ " Peter Sent from Mail for Windows 10 From: Manjukumar Harthikote Matha Sent: 27 December 2016 19:20 To: Peter Smith; [email protected] Subject: RE: [meta-xilinx] Failure building Docker with Yocto 2016.4 Hi Peter, > -----Original Message----- > From: [email protected] [mailto:meta-xilinx- > [email protected]] On Behalf Of Peter Smith > Sent: Monday, December 26, 2016 2:33 PM > To: [email protected] > Subject: Re: [meta-xilinx] Failure building Docker with Yocto 2016.4 > > Here is the link > https://lists.yoctoproject.org/pipermail/meta-virtualization/2016- > December/002143.html > > On 26 Dec 2016 10:23 pm, "Peter Smith" <[email protected] > <mailto:[email protected]> > wrote: > > > One of my colleagues reported a failure to build Docker using Xilinx's > meta- > petalinux based Yocto flow image petalinux-minimal as described on Xilinx's > wiki (see > the December archive of the meta-petalinux list, apologies for not including > link, > typing this on a phone). I have repeated the problem using the 2016.4 > branches (still > based on Krogoth I belive). Yes 2016.4 is based on Krogoth. Are you using Xilinx SDK toolchain? Ubuntu 14.04 was an unsupported host OS for Xilinx release. I have to check and see if there was any issue with the build on Ubuntu 14.04. Have you seen this issue with any other host OS (Ubuntu 15.04 or 16.04?) We use meta-virtualization layer as is, other than removing an error during architecture check ( https://gitenterprise.xilinx.com/Yocto/meta-petalinux/blob/prod-rel-v2016.4/classes/go-osarchmap.bbclass) >The maintainer on the other list stated he could not > repeat with his setup, I conclude from this that there is some issue related > to > including meta-petalinux in bblayers, the maintainers working example did not > include this layer. Thanks Manju This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately. This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately. -- _______________________________________________ meta-xilinx mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-xilinx
