[rtems-crossrpms commit] Reflect arm-rtems being history.

Joel Sherrill joel.sherrill at OARcorp.com
Sun Apr 29 13:36:48 UTC 2012

I would have thought by now you would hhave understood the right thing to do. Let me explain it once again:

+ CPU-rtems ALWAYS exists and is the recommended primary toolset
+ During transition periods. CPU-rtemsXXX may be needed as a safety net for the older target configuration

In this particular situation, we have 3 target names:

+ arm-rtems - was ELF should be switched to EABI
+ arm-rtemself - needed to have old target available as backup
+ arm-rtemseabi - needed to have new version

There should be binaries for arm-rtems and whatever is the secondary (whether coming or going) format. 

This was done multiple times for a.out to coff and coff to elf transitions.

Ralf did you not understand what to do or are you deliberately being childish difficult? Given your behavior in general, I know my opinion.

Packaging the tools is supposed to be a service to the community not a way to dictate to developers what to use as host OSes or object format. Listen to those who are daily using RTEMS to do their jobs and build systems. Users define the requirements for RTEMS itself. Do the same for the tools.


Ralf Corsepius <ralf at rtems.org> wrote:

>Module:    rtems-crossrpms
>Branch:    master
>Commit:    3da87ee7f18c1f9a680de0f7891c49506035a1e8
>Changeset: http://git.rtems.org/rtems-crossrpms/commit/?id=3da87ee7f18c1f9a680de0f7891c49506035a1e8
>Author:    Ralf Corsépius <ralf.corsepius at rtems.org>
>Date:      Fri Apr 27 12:07:53 2012 +0200
>Reflect arm-rtems being history.
> .gitignore |    1 -
> 1 files changed, 0 insertions(+), 1 deletions(-)
>diff --git a/.gitignore b/.gitignore
>index 327a1f4..1a66d6d 100644
>--- a/.gitignore
>+++ b/.gitignore
>@@ -4,7 +4,6 @@
> /config.status
> /cygwin*/*/rtems-4.11*.spec
> /mingw32/*/rtems-4.11*.spec
> /rtems4.11/arm-eabi/arm-*.spec
> /rtems4.11/avr/avr-*.spec
> /rtems4.11/bfin/bfin-*.spec
>rtems-vc mailing list
>rtems-vc at rtems.org

More information about the devel mailing list