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

Thomas Doerfler Thomas.Doerfler at embedded-brains.de
Sun Apr 29 17:03:27 UTC 2012


Joel, Ralf,

when looking at GCC4.7 documentation

http://gcc.gnu.org/gcc-4.7/changes.html

there is a list of obsoleted ARM target with their supported alternatives:

----------------
The obsolete ports with alternatives are:

    arm*-*-rtems (use arm*-*-rtemseabi)
    arm*-*-linux-gnu (use arm*-*-linux-gnueabi)
    arm*-*-elf (use arm*-*-eabi)
    arm*-*-uclinux* (use arm*-*-uclinux*eabi)

--------------------------
When looking at the "linux-gnu" and "uclinux" versions which did not
specify a special ABI or object format, gcc obviously prefers to have
the term "eabi" in the new target name.

Joel, this is not what we defined for the ARM toolset transition, but we
decided to follow GCC with the ABI transition, so I think it makes sense
to also stick to their naming convention. What's the real problem with
the naming?

wkr,

Thomas.

Am 29.04.2012 15:36, schrieb Joel Sherrill:
> 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.
> 
> --joel
> 
> 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/arm-*.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
>> http://www.rtems.org/mailman/listinfo/rtems-vc
> 
> _______________________________________________
> rtems-devel mailing list
> rtems-devel at rtems.org
> http://www.rtems.org/mailman/listinfo/rtems-devel


-- 
--------------------------------------------
Embedded Brains GmbH
Thomas Doerfler           Obere Lagerstr. 30
D-82178 Puchheim          Germany
email: Thomas.Doerfler at embedded-brains.de
Phone: +49-89-18908079-2
Fax:   +49-89-18908079-9



More information about the devel mailing list