I have been working toward getting a "modern" cross compiling toolchain
included in Fedora[0] ever since mspgcc stopped working[1] 4 years ago.
Up until recently, my efforts have been almost entirely centered around
packaging TI / Mitto Systems' somewhat bespoke branch of GCC[2].
It has been suggested[3] that my efforts may be better focused on having
msp430-none-elf (and possibly msp430-none-elf-bare) added as an arch to
the cross-gcc / cross-binutils packages. This would require building a
msp430-none-elf-newlib package as well.
I have managed to build modified cross-gcc and cross-binutils packages
with a matching newlib package. Code compiles and links, but the
resulting binary does not actually work on the micro. I suspect the
correct linker script is not being used, but I have not had time to
investigate further and am somewhat over my head in building and
troubleshooting cross compilers.
Which path forward is recommended? Option one, the bespoke branch,
already produces a working toolchain[4]. Option two, modified cross-gcc
/ cross-binutils has a lot more appeal being 'vanilla' upstream, and
adds the possibility of supporting the 'bare' msp430 target, but I'm a
bit lost in how to get the parts to produce a functional binary.
[0] - https://bugzilla.redhat.com/show_bug.cgi?id=1350884
[1] - https://bugzilla.redhat.com/show_bug.cgi?id=1175942
[2] - https://www.ti.com/tool/MSP430-GCC-OPENSOURCE
[3] -
https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx/message/KAYAKXOY7ZPQEENB6PUM2EEUN53X2HQQ/
[4] -
https://copr.fedorainfracloud.org/coprs/nielsenb/msp430-development-tools/
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
