[meta-xilinx] Failure building Docker with Yocto 2016.4

[Manjukumar Harthikote Matha]

Hi Peter,

> -----Original Message-----
> From: meta-xilinx-bounces at yoctoproject.org [mailto:meta-xilinx-
> bounces at yoctoproject.org] On Behalf Of Peter Smith
> Sent: Monday, December 26, 2016 2:33 PM
> To: meta-xilinx at yoctoproject.org
> 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" <salerio at gmail.com
> <mailto:salerio at gmail.com> > 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.