[meta-xilinx] Differences between Yocto meta-xilinx and Xilinx meta-xilinx

[SMITH Peter T]

Yes, will use 2016.3 tool chain.

-----Original Message-----
From: Manjukumar Harthikote Matha [mailto:manjukumar.harthikote-matha at xilinx.com]
Sent: 01 November 2016 16:03
To: SMITH Peter T; meta-xilinx at yoctoproject.org
Subject: RE: [meta-xilinx] Differences between Yocto meta-xilinx and Xilinx meta-xilinx

Hi Peter

> -----Original Message-----
> From: SMITH Peter T [mailto:peter.t.smith at alstom.com]
> Sent: Tuesday, November 01, 2016 8:49 AM
> To: Manjukumar Harthikote Matha; meta-xilinx at yoctoproject.org
> Subject: RE: [meta-xilinx] Differences between Yocto meta-xilinx and
> Xilinx meta- xilinx
>
> Manju, I will try with Xilinx toolchain, should I follow the
> instructions for configuring this as per the Xilinx Wiki i.e. using
> external tool chain? Peter

Yes that would work.
I hope you have got the latest Xilinx SDK toolchain as a part of 2016.3 tools https://urldefense.proofpoint.com/v2/url?u=https-3A__www.xilinx.com_support_download_index.html_content_xilinx_en_downloadNav_embedded-2Ddesign-2Dtools.html&d=DQIFAg&c=IV_clAzoPDE253xZdHuilRgztyh_RiV3wUrLrDQYWSI&r=-0xOp6WEUxZEZ28IafXrMa3oLhGTFvyj7y8nzyNrgGo&m=GKLttDyeplFk6AGIeiovybsoYfmTJKFNq8DJ1m5MdEY&s=zbLU7lrbHpFLwVI_37lLoR3lwUOCoY5OWB9adyMz-Xs&e=

Thanks
Manju


>
> -----Original Message-----
> From: Manjukumar Harthikote Matha [mailto:manjukumar.harthikote-
> matha at xilinx.com]
> Sent: 01 November 2016 15:47
> To: SMITH Peter T; meta-xilinx at yoctoproject.org
> Subject: RE: [meta-xilinx] Differences between Yocto meta-xilinx and
> Xilinx meta- xilinx
>
> Hi Peter
>
> > -----Original Message-----
> > From: SMITH Peter T [mailto:peter.t.smith at alstom.com]
> > Sent: Tuesday, November 01, 2016 8:33 AM
> > To: Manjukumar Harthikote Matha; meta-xilinx at yoctoproject.org
> > Subject: RE: [meta-xilinx] Differences between Yocto meta-xilinx and
> > Xilinx meta- xilinx
> >
> > Manu,
> >
> > I have tried building "core-image-minimal" with meta-xilinx (branch
> > rel-v2016.3 from Xilinx Git repo) and get a compilation error building ATF.
> > Log file is below. I used Krogoth branch of poky from Yocto git repo.
> > Am I doing anything wrong here or have I uncovered a gremlin?
> >
> We use Xilinx SDK toolchain (based of meta-linaro toolchain) and don't see this issue.
> However there was an issue with binutils 2.26 which is creating this
> issue A fix was posted here,
> https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__github.com_ARM-2Dsoftware_arm-2Dtrusted-
> 2Dfirmware_commit_79627dc37259781e578c47e1e63856dd0424b2a2&d=DQIFAg&
> c=IV_clAzoPDE253xZdHuilRgztyh_RiV3wUrLrDQYWSI&r=-
> 0xOp6WEUxZEZ28IafXrMa3oLhGTFvyj7y8nzyNrgGo&m=kRAYsm_XjamoQ3ZTBs_y5a
> w9ExXvIpwDzNlvd_78MDA&s=5PFiDQnFqhS8BIHL7L4vvf6DyIfAn6t9OBseErD8rbM&e
> =
>
> I think we need to backport this patch with 2016.3 branch and Yocto
> toolchain <...>
>
> 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.
>
>
> ________________________________
> CONFIDENTIALITY : This e-mail and any attachments are confidential and
> may be privileged. If you are not a named recipient, please notify the
> sender immediately and do not disclose the contents to another person,
> use it for any purpose or store or copy the information in any medium.


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.


________________________________
CONFIDENTIALITY : This e-mail and any attachments are confidential and may be privileged. If you are not a named recipient, please notify the sender immediately and do not disclose the contents to another person, use it for any purpose or store or copy the information in any medium.