Notice: We have migrated to GitLab launching 2024-05-01 see here: https://gitlab.rtems.org/

#3912 assigned task

Describe relationship between RTEMS and gcc cross-compiler

Reported by: Gedare Bloom Owned by: Needs Funding
Priority: normal Milestone: Indefinite
Component: doc Version:
Severity: normal Keywords: small, tasks
Cc: Blocked By:
Blocking:

Description (last modified by Gedare Bloom)

Occasionally new users are confused why they can't use their distributions cross-compiler for their target, e.g., the riscv64-linux-gnu or the arm-none-eabi-gcc. This task is to write a paragraph or two in the User's Guide to explain why this doesn't work.

You will need to identify a good place in the guide to put this information, and work with the community to understand the restrictions. Probably somewhere near the start of the user's guide or in the quick start will be good.

At a high-level, the reasons that one must use the rtemsX-gcc are:

  • newlib will be configured correctly for rtems, which is where much of our POSIX and libc support comes from.
  • threading in GCC support libraries is tailored to RTEMS
  • to provide the preprocessor define __rtems__

There may be some other small reasons that could come up from discussion.

Change History (3)

comment:1 Changed on 03/19/20 at 22:36:30 by Gedare Bloom

Description: modified (diff)

comment:2 Changed on 03/19/20 at 22:37:39 by Gedare Bloom

Keywords: tasks added; task removed

comment:3 Changed on 03/20/20 at 03:35:42 by Chris Johns

Plus specific multilib variants to match BSPs

Note: See TracTickets for help on using tickets.