Kunal Singh wrote:
hi,
I figured out the problem. The Diab compiler adds an underscore in front
of all the symbol.
I could partially resolve the problem by calling _FUNCTION_NAME from my
application.
However, now I have another problem.
The code compiled with Diab uses some functions from C-Lib.
These calls now require _memcpy() and _memset() functions to be available.
However the ulibC available on my target will only provide memcpy() and
memset() functions.
One possible way to resolve this issue could be to write my own
_memcpy() and _memset() [just a wrapper around memcpy and memset].
But I guess this is the most ugly way as the function calls involve
unnecessary loops, and for if the code has too many external
dependencies, I will have to keep on writing new wrappers.
Can some guide me on:
(1) How I can force the Diab compiler not to add an extra underscore in
fron of symbol names?
(2) If a is not possible, can I modify the symbol names in the library
file to strip off the extra underscore? Will it break anything?
As a suggestion #define _memcpy memcpy and #define _memset memset or
vice versa and use GNU C. I though you were porting away from diab?
hth - bob
--
*Robert Warner*
*Senior Embedded Systems Development Engineer*
*Kutta** Technologies*
Mobile: 734-355-3547
Office: 602.896.1976, Ext.242
Fax: 602.896.1007
[EMAIL PROTECTED]
www.kuttatech.com <http://www.kuttatech.com/>
Kutta Tech <http://www.kuttatech.com>
_______________________________________________
uClinux-dev mailing list
[email protected]
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by [email protected]
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev
