09-10-2019 03:08 PM
From 2018.3 to 2019.1, what happened to the aarch64-linux-gnu-* toolchain?
What are we supposed to use in their stead?
Why nothing in release notes?
09-10-2019 03:15 PM
09-11-2019 08:16 AM
I will try that.
BUT, is that the intended replacement for the aarch64-linux-gnu-* toolchain? AND, is that documented anywhere?
09-11-2019 03:13 PM
It seems unintentioanl deployment issue of cross compiler tool chain.
If forgot some setting like "linux-gnu", it occured.
I guess it is build by CI tool on like docker.
So, I guess, nobody announce this change... Not documented...
09-23-2019 10:43 PM - edited 09-24-2019 12:22 AM
Since petalinux is based out of yocto build system, we should use toolchains delivered by yocto, those will come while building project.
Petalinux wont use those from tool and removed in 2019.1
You can use SDK if you want this toolchain in particular. Here is the SDK toolchain path:
09-24-2019 07:23 AM
"Petalinux wont use those from tool" ... What is meant here?
So you're saying that Petalinux does not use this partiucular toolchain any longer? It used to as I gleaned that particular compiler from a build log building an application out of a Petalinux log. It would be really nice if Xilinx made a change of this magnitude and passed it along in their release notes.
Secondly, you're saying that to access that previous toolchain I use an SDK path? Is that going to be compatible with the Petalinux libs? If I build an application out of Petalinux it won't use that compiler correct?
I'm having a fair amount of trouble understanding what y'all did here.