cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Visitor
Visitor
467 Views
Registered: ‎02-06-2019

2019.1 Missing Tools?

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?

0 Kudos
5 Replies
Highlighted
Mentor
Mentor
464 Views
Registered: ‎06-16-2013

Re: 2019.1 Missing Tools?

Hi @pmccumber 

 

Would you check the following directory ?

 

<petalinux install directory>/tools/xsct/gnu/aarch64/lin/aarch64-none/bin

 

Best regards,

0 Kudos
Highlighted
Visitor
Visitor
412 Views
Registered: ‎02-06-2019

Re: 2019.1 Missing Tools?

I will try that.  

BUT, is that the intended replacement for the aarch64-linux-gnu-* toolchain?   AND, is that documented anywhere?

0 Kudos
Highlighted
Mentor
Mentor
394 Views
Registered: ‎06-16-2013

Re: 2019.1 Missing Tools?

Hi @pmccumber 

 

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...

 

Best regards,

0 Kudos
Highlighted
Moderator
Moderator
296 Views
Registered: ‎12-04-2016

Re: 2019.1 Missing Tools?

Hi 

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:

SDK/2019.1/gnu/aarch32/lin/gcc-arm-linux-gnueabi

 

 

Best Regards

Shabbir

0 Kudos
Highlighted
Visitor
Visitor
272 Views
Registered: ‎02-06-2019

Re: 2019.1 Missing Tools?

"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.

0 Kudos