mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
* [ptxdist] Using a different toolchain for certain packages
@ 2026-07-16  8:09 Guillermo Rodriguez Garcia
  2026-07-16 12:34 ` Christian Melki
  0 siblings, 1 reply; 2+ messages in thread
From: Guillermo Rodriguez Garcia @ 2026-07-16  8:09 UTC (permalink / raw)
  To: ptxdist; +Cc: Alejandro Vazquez

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
guille.rodriguez@gmail.com



^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [ptxdist] Using a different toolchain for certain packages
  2026-07-16  8:09 [ptxdist] Using a different toolchain for certain packages Guillermo Rodriguez Garcia
@ 2026-07-16 12:34 ` Christian Melki
  0 siblings, 0 replies; 2+ messages in thread
From: Christian Melki @ 2026-07-16 12:34 UTC (permalink / raw)
  To: Guillermo Rodriguez Garcia; +Cc: Alejandro Vazquez, ptxdist

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 guille.rodriguez@gmail.com. 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
> guille.rodriguez@gmail.com
> 




^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2026-07-16 12:35 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2026-07-16  8:09 [ptxdist] Using a different toolchain for certain packages Guillermo Rodriguez Garcia
2026-07-16 12:34 ` Christian Melki

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox