Page MenuHomeSolus

Closed, WontfixPublic

BearzR created this task.Aug 31 2016, 2:04 AM

For what reason? Solus is x86_64 only.

I'm in a robotics team (FRC) and do all my programing in c++. We have to program a device called the RoboRIO witch is an arm based Linux device. All my code gets cross compiled over to arm from my laptop using eclipse as the IDE and GCC set up for arm under the Hood.They provide their own tool-chain but all it is a GCC set up to cross compile to arm with frc- in front of the executable. It pretty Much the same concept as the Arduino with AVR support, it gets compiled on the computer and then pushed to the device by a serial connection.

Tick added a subscriber: Tick.Sep 1 2016, 1:25 PM
DataDrake triaged this task as Normal priority.Sep 10 2016, 2:06 PM

The source downloads for the gcc-arm-none-eabi are have moved to as per the note on the launchpad page.


I'll just note that this is pretty vital in developing for ARM microcontrollers. Normal workflow with the OpenSTM32 toolchain in my case, has the plugins installer try to handle everything but fail because it explicitly requires the 32-bit C shared libraries and compiler.

So I gave it a try today, but I'm not sure how to proceed. The aforementioned toolchain contains everything (GNU C/C++ Compiler, Binutils, GDB and Newlib) and looks like it's thought to build it on your own since the scripts pull all needed packages without any checksum verification.
The other way would be to provide the single packages - when you take a look at the "arch enemy", they provide:

  • arm-none-eabi-binutils
  • arm-none-eabi-gcc
  • arm-none-eabi-gdb
  • arm-none-eabi-newlib

all built from their respective source. I think the latter would be preferred, but since I wouldn't be using it I wait for someone's answer :)

JoshStrobl closed this task as Wontfix.Jun 25 2018, 1:06 PM
JoshStrobl added a project: Needs Maintainer.
JoshStrobl claimed this task.
JoshStrobl added a subscriber: JoshStrobl.

This has sat in accepted for inclusion for over a year. Clearly, there is a lack of demand for the inclusion of this software, nobody has stepped up to provide a patch, maintain it, and properly integrate it. Closing as a result. Feel free to reopen but only when someone offers a patch via our proper patch submission methods and volunteers to be maintainer.