[meta-freescale] Significance of the fslc vendor field in arm-fslc-linux-gnueabi-gcc

[Phil Williams]

Hello,

What is the significance of the vendor being set to fslc in the
toolchain? Is it simply a label, or does it have some compatibility
differences (compared with -unknown-).

The reason I ask is because I was wondering if there would be any issues
using off the shelf Rust or Go compilers and specifying the target as
arm-unknown-linux-gnueabi.

Thanks,

Phil

--

[Daiane Angolini]

Post by Phil Williams
Hello,
What is the significance of the vendor being set to fslc in the
toolchain? Is it simply a label, or does it have some compatibility
differences (compared with -unknown-).

I don't think there is any significant change. But I would recommend
you make some tests for your use-case.

Daiane

Post by Phil Williams
The reason I ask is because I was wondering if there would be any issues
using off the shelf Rust or Go compilers and specifying the target as
arm-unknown-linux-gnueabi.
Thanks,
Phil
--
_______________________________________________
meta-freescale mailing list
https://lists.yoctoproject.org/listinfo/meta-freescale

--

[Otavio Salvador]

Post by Phil Williams
What is the significance of the vendor being set to fslc in the
toolchain? Is it simply a label, or does it have some compatibility
differences (compared with -unknown-).
The reason I ask is because I was wondering if there would be any issues
using off the shelf Rust or Go compilers and specifying the target as
arm-unknown-linux-gnueabi.

Currently, the fslc distribution does not change anything that might
conflict with those, as far as I know, but you should keep an eye on
the distribution changes to spot any possible conflicting changes in
future.

Usually, the vendor is used globally so you ensure it is compatible
across the whole system. Rust and Go are less fragile in this regard
as it links most libraries (modules and crates) on same binary but
differences on libc or features may cause problems.