• State Not Answered
  • Locked Locked
  • Replies 0 replies
  • Subscribers 21 subscribers
  • Views 665 views
  • Users 0 members are here
2025 survey

We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.

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

GCC build problems

Liam Staskawicz

I'm having trouble adapting a Makefile-based build to uVision 4 for my cortex-m3 target. I have (I think) all the compile settings pulled in, but the link is failing on some libc-related stuff. I'm using the latest GCC 4.5.0-based yagarto toolchain, and seeing the link error:

c:/yagarto/bin/../lib/gcc/arm-none-eabi/4.5.0/../../../../arm-none-eabi/bin/ld.exe: error: Source object c:/yagarto/bin/../lib/gcc/arm-none-eabi/4.5.0/../../../../arm-none-eabi/lib\libc.a(lib_a-memset.o) has EABI version 5, but target buildtest.elf has EABI version 0

c:/yagarto/bin/../lib/gcc/arm-none-eabi/4.5.0/../../../../arm-none-eabi/bin/ld.exe: failed to merge target specific data of file c:/yagarto/bin/../lib/gcc/arm-none-eabi/4.5.0/../../../../arm-none-eabi/lib\libc.a(lib_a-memset.o)

I've confirmed that in the Makefile build, it's linking against arm-none-eabi/lib/v7m/libc.a instead, and I've definitely specified -mcpu=cortex-m3. Any tips on why the uVision-based build wants to link against arm-none-eabi/lib\libc.a?

Secondary issue

Is it possible to view the full build output? Currently, the only output I see is summarized: "compiling syscalls.c..." etc. I realize that the tabs in the project settings show what is going to be passed to the compiler, but I'd sure like to see it happening myself so I can diagnose problems a little more easily.

Thanks!