Please note: We are aware of an issue affecting replies on the Arm Community forums, which may not be loading as expected.

We apologize for any inconvenience and appreciate your patience while we investigate and work to resolve the issue.

Thank you for your understanding.

  • State Suggested Answer
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 119 subscribers
  • Views 27984 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

using vsprintf() in my code is creating linking issues .

Azar

Hello,

When I include vsprintf() for printing on hyperterminal , my build is throwing the below issue during linking .

lkarm E106: unresolved external: __aeabi_fcmpeq - (_doflt.obj)

Building source file IfxScuLbist.c for Tricore

lkarm E106: unresolved external: __aeabi_fcmpgt - (_doflt.obj)

lkarm E106: unresolved external: __aeabi_f2iz - (_doflt.obj)

lkarm E106: unresolved external: __aeabi_fmul - (_doflt.obj)

lkarm E106: unresolved external: __aeabi_fadd - (modff.obj)

Can anyone help me with this . ?

Parents
  • 0 Arm Employee Badge

    Hi Azar

    Which toolchain are you using? "lkarm" is not a linker provided with the Arm Development Studio or Keil MDK, so this forum might not be the best place to help you.

    Are you linking with AEABI-compliant C libraries? It looks like your linker cannot find the __aeabi_* functions - are they present in your C library?

    Stephen

Reply
  • 0 Arm Employee Badge

    Hi Azar

    Which toolchain are you using? "lkarm" is not a linker provided with the Arm Development Studio or Keil MDK, so this forum might not be the best place to help you.

    Are you linking with AEABI-compliant C libraries? It looks like your linker cannot find the __aeabi_* functions - are they present in your C library?

    Stephen

Children