• Locked Locked
  • Replies 5 replies
  • Subscribers 121 subscribers
  • Views 4752 views
  • Users 0 members are here
Options
Related
How was your experience today?
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
Offline
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
  • Offline
    Note: This was originally posted on 16th May 2013 at http://forums.arm.com

    I am not using the -flto option.

    I am not sure if EABI mismatch would cause a problem in program execution as such but I was under the impression that  objects of different EABI versions are incompatible.

    Anyway, still I tried using "[size=2]--no-warn-mismatch" in my GNU makefile, it gives me following error[/size]

    arm-elf-gcc: error: unrecognized option '--no-warn-mismatch'
Reply
  • Offline
    Note: This was originally posted on 16th May 2013 at http://forums.arm.com

    I am not using the -flto option.

    I am not sure if EABI mismatch would cause a problem in program execution as such but I was under the impression that  objects of different EABI versions are incompatible.

    Anyway, still I tried using "[size=2]--no-warn-mismatch" in my GNU makefile, it gives me following error[/size]

    arm-elf-gcc: error: unrecognized option '--no-warn-mismatch'
Children
No data