this symbol problem happens to me after i had sucessfully used CCS5.1M8 and now installed the latest version
This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
this symbol problem happens to me after i had sucessfully used CCS5.1M8 and now installed the latest version
Did you import the same project that built fine with 5.1M8 into 5.1RC1 and ran into this error?
Are you building for EABI, and is the project set for automatic runtime library selection (in Project Properties->CCS Build)? Can you provide the full list of compiler/linker options?
There is a related thread which might be helpful, but if that does not help, would you be able to provide the project that generates this error? In the meantime, I'll try to reproduce this error as well.
i am using EABI (seems COFF is labled "legacy" in CCS dialogs).
i tried "--cinit_compression=off" and it resolved the problem.
via CCS project menu: "Linker" -> "Linktime Optimisation" -> "Compress ELF C style auto initialisation" -> "off" (wondering why there is no drop down box)
the c-library was probably rebuilt on the fly for my specific "TI8" target. no clue why exactly that symbol was missing from the libc build results.
i suppose those library should in any normal case come with compression support by default. if the symbol is not needed, the linker should be in duty to strip it, not the programmer. but for this the symbol must be there in the first row, especially for cases where the programmer wants to use it.
Alexander,
Are you able to share the project that is giving you this undefined symbol error? We'd like to look into this further to see if the linker is in error here.
I sent you a friend request. When you accept, you can start a private conversation with me and attach the prjoect there.
Alex,
As we discussed offline, since this problem was not reproducible at TI with the same set of files, we will hold off on investigating this further. If you're able to reproduce this in a clean 5.1RC1 installaiton or get better insight into how the problem is triggered, then please feel free to let us know.
Hi AartiG,
I encountered the same issue. And it can be solved by the same work around. Do you need me to share the prj to you to test it ?
I am working on CCS 5.1.1.0031.
Regards,
Eason
Eason Wang said:I encountered the same issue. And it can be solved by the same work around. Do you need me to share the prj to you to test it ?
Yes, if this is reproducible with a small test case that you can share that would be great. Please zip up the entire proejct folder and attach it here or if you prefer, you can start a private conversaton with me and sending it that way.