• Locked Locked
  • Replies 5 replies
  • Subscribers 118 subscribers
  • Views 5518 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Setting output EABI version in RVCT3.1

Sneha Pallapotu
Note: This was originally posted on 15th May 2013 at http://forums.arm.com

Hi I am using a library built with RVCT3.1 and linking it to my linux application using arm-elf-gcc-4.6.1, I am getting an error of EABI versions mis-match.

RVCT3.1 generates a EABI version 5 and arm-elf-gcc is giving a EABI version 0, Is there a way to set the RVCT output EABI version (to make it backward compatible)
or to set the arm-elf-gcc EABI version to make the library and application objects compatible.
Parents
  • Note: This was originally posted on 17th May 2013 at http://forums.arm.com

    Thanks scott. The solution worked and I am able to get my final library after partial linking..Will check if the version mismatch is causing any problem while running..

    but observed a strange behavior: the error message I was getting earlier said

    error: Source object *.o has EABI version 5, but target ../lib/*.a has EABI version 0

    But Now after building with option --no-warn-mismatch, when I check the EABI version of generated *.a, its GNU  EABI 4 !!!
    Any idea why this discrepancy?
Reply
  • Note: This was originally posted on 17th May 2013 at http://forums.arm.com

    Thanks scott. The solution worked and I am able to get my final library after partial linking..Will check if the version mismatch is causing any problem while running..

    but observed a strange behavior: the error message I was getting earlier said

    error: Source object *.o has EABI version 5, but target ../lib/*.a has EABI version 0

    But Now after building with option --no-warn-mismatch, when I check the EABI version of generated *.a, its GNU  EABI 4 !!!
    Any idea why this discrepancy?
Children
No data