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

Error use gcc linking  RVCT2.2 c libraries

Note: This was originally posted on 19th March 2007 at http://forums.arm.com

I use RVCT2.2 armcc to complier files and get a library.
Then to use gcc link the library, but get
Error:
  undefined reference to '__aeabi_uread4'
  undefined reference to '__aeabi_uwrite4'

I know that the armcc and gcc are different to link the fwrite() or fread() functions,
RVCT 2.2  armcc use an optimized one, i,e. __aeabi_

But , how to solve such problem? 
Have  any simple armcc compiler options to avoid such questions?

Any suggestion approciated.

Parents
  • Note: This was originally posted on 30th March 2007 at http://forums.arm.com

    I had the same problem and i tried the code sourcery's gcc. All _aeabi errors are cleared. but i got another error:

    "conflicting defenitions of wchar_t "

    but I'm not using any wide chars in my code. Is there any solution for that error? Is it a compiler issue?


    Two toolchains may use different size containers for the wchar_t type and linking objects with different sizes will cause problems at run-time if you ever use them.  You'll need to make sure the objects you generate have the right type for the library you'll be linking with.  Check the documentation for the compiler for a switch that could let you change this.

    Alternatively, if you are sure there are no wchar_t use in your code and the library you may be able to suppress the error when linking.  Check the options for the linker.
Reply
  • Note: This was originally posted on 30th March 2007 at http://forums.arm.com

    I had the same problem and i tried the code sourcery's gcc. All _aeabi errors are cleared. but i got another error:

    "conflicting defenitions of wchar_t "

    but I'm not using any wide chars in my code. Is there any solution for that error? Is it a compiler issue?


    Two toolchains may use different size containers for the wchar_t type and linking objects with different sizes will cause problems at run-time if you ever use them.  You'll need to make sure the objects you generate have the right type for the library you'll be linking with.  Check the documentation for the compiler for a switch that could let you change this.

    Alternatively, if you are sure there are no wchar_t use in your code and the library you may be able to suppress the error when linking.  Check the options for the linker.
Children
No data