Hello Guillermo. I suggest not getting to hung up on compiler triplets. You'd be fine compiling TF-A with something that has a OS/C-library interface, like Linux. You can steer away your compiler from using that interface.
And yes, afaik, ptxdist supports different toolchains for various packages. You can for example look on how the pre/kernel.make and pre/bootloader.make do it. That would be the typical suspects. I routinely add the selected_toolchain_kernel to my projects although it has been a long time since I needed a separate one. It was mostly vendor kernels stuck on _old_ stuff that wouldn't build with a newer compiler. Regards, Christian On 7/16/26 10:09 AM, Guillermo Rodriguez Garcia wrote: > [Du får inte e-post ofta från [email protected]. Läs om varför det > här är viktigt på https://aka.ms/LearnAboutSenderIdentification ] > > Hello, > > We have a BSP that uses an arm-linux-gnueabihf toolchain, and are > having some issues when compiling TF-A with the same toolchain. > > While we managed to work around the problems that we found, we noticed > that the TF-A docs officially recommend using an arm-none-eabi > toolchain > (https://trustedfirmware-a.readthedocs.io/en/latest/getting_started/prerequisites.html#toolchain). > > Does PTXdist support using a different toolchain for specific packages? > > Thanks, > > Guillermo Rodriguez Garcia > [email protected] >
