build stuck: rtems-4.10.2, arm-elf, nds

Ralf Corsepius ralf.corsepius at
Wed Apr 10 14:30:26 UTC 2013

On 04/10/2013 03:04 PM, Matt Wette wrote:
> On Apr 9, 2013, at 11:20 PM, Ralf Corsepius wrote:
>> On 04/10/2013 04:18 AM, Matt Wette wrote:
>>> I'm looking for hints.
>>> I built tools, then configure rtems-4.10.2 for --target=arm-elf, then make RTEMS_BSP=nds
>> Why are you trying this?
>> * "arm-elf" is not a valid target tuple for RTEMS
>> * "arm-elf" built-GCC toolchains are addressing an entirely different systems (Usually OS-less, bare-metal targets).
> Can you be more explicit?
The RTEMS toolchains setup contains specialized binutils/gcc/gdb and 
newlib setups.

=> configuring for arm-elf is something completely different as 
configuring for arm-rtems*.

To put it differently: Though an arm-elf/newlib targeted toolchain is 
very similar to arm-rtems*, it basically is as different as a linux 
toolchain would be compared to a windows toolchains.

>   I used "./configure --prefix=/opt/rtool-4.10 --target=arm-elf" for binutils, gcc, newlib, gdb.
> The config for rtems seemed to find the compiler fine.    Has anyone built the toolchain?
> I never tried --target=elf-rtems4.10 because I thought this would happen:
> localhost$ ./configure --prefix=/opt/rtool-4.10 --target=arm-rtems-4.10
> checking build system type... x86_64-unknown-linux-gnu
> checking host system type... x86_64-unknown-linux-gnu
> checking target system type... Invalid configuration `arm-rtems-4.10': system `4.10' not recognized
> configure: error: /bin/sh ./config.sub arm-rtems-4.10 failed
--target=arm-rtems4.10 would be correct (no blank)


More information about the users mailing list