Topic : RIDE7 Make failure

Forum : Ride IDE

Original Post
Post Information Post
June 16, 2009 - 8:27am

I have installed the latest version of RIDE7 and RKIT Arm.
At the end of compilation, during the link phase the RIDE report me an error like this:

Running: LD
\"C:\Programmi\Raisonance\Ride\arm-gcc\bin\arm-none-eabi-gcc.exe" -mcpu=arm966e-s -Wl,-T -Xlinker "D:\Works\EXEL\PROJECTS\Tecnoelettra\TE-808\Projects\Firmware\FW\FWs\FW\obj\TE808.elf.ld" -u _start -Wl,-static -Wl,--gc-sections -nostartfiles -Wl,-Map -Xlinker "D:\Works\EXEL\PROJECTS\Tecnoelettra\TE-808\Projects\Firmware\FW\FWs\FW\lst\"
c:/programmi/raisonance/ride/arm-gcc/bin/../lib/gcc/arm-none-eabi/4.3.2/../../../../arm-none-eabi/lib\libc.a(lib_a-isattyr.o): In function `_isatty_r':
isattyr.c:(.text+0x18): undefined reference to `_isatty'
collect2: ld returned 1 exit status

Build failed
and the process fails.
How caan i solve this problem?
Best regards.

Post Information Post
June 16, 2009 - 9:22am

i roll-back the RKIT ARM to version 1.16.0930 and now the RIDE7 build.

At the end of compilation the RIDE7 always crash .

June 17, 2009 - 12:06pm


I had the same problems ( see my previous post ) and my solution was as follows :

1) install the latest version of Ride7 and RKitArm that are now on the website.

on my systems that solved the crash at the end of the build

2) for the undefined reference you need an older version the libraries of RKitArm

I copied the whole directory 'C:\Program Files\Raisonance\Ride\arm-gcc\arm-none-eabi\lib'
from a computer with a working installation of Ride7 and RKitArm to the computer that
has undefined reference error

The working release that i had was from the RKIT_ARM_BN29 release that i downloaded in februari.

I use a STR710FZ2 and that works ok with those libraries but if you have an other processor you might need
an other version of the libraries.

My general advise for updating Ride and RKitArm is to use a virtual machine ( i use VMWare 1) with a standard
installation of WindowsXP (i don't like Vista ) and install the new versions in the virtual machine and then try
to compile your project with the new release.

It means more work for testing but if the new version does not work for you it's only in the virtual machine and
you still have a working computer with the previous version you were using.

I hope this helps

Kind Regards,
Ed van Rijn