Compiling libflame Library for bare metal on A53

[khana...@gmail.com]

Hi All,
I am trying to compile the "libflame" library code for A53 and use it on bare metal (without any OS). There are issues when I am executing my elf which has statically linked the "libflame.a". During debug I found the library is using sprintf which is generating some incorrect address. It seems the libc used by the libflame.a is not correct. Can someone help me on this to find out the correct configuration/compilation flags. I am using the aarch64-elf-gcc toolchain from Linaro. (gcc version 6.3.1 20170109 (Linaro GCC 6.3-2017.02))

Thanks & Regards
Asif

[Field G. Van Zee]

Asif,

Thanks for your interest in libflame.

I don't know anything about "bare metal" builds, but if you have correctly
diagnosed the problem as the wrong libc being linked, then I suspect the
problem is not with libflame. I could be mistaken, but I believe your compiler
chooses the C library at link time and that neither libflame's source code nor
its build system affect that decision.

Perhaps others on the list can chime in.

Field

[Asif Khan]

Thanks a lot Field,

     I have diagnosed the problem and executed "libflame" on bare metal (A53). The issue was related to semihosting. I had to over ride the functions of studio.h with my own functions, this has resolved the issue. Thanks again for your kind help.

Regards

Asif

--
You received this message because you are subscribed to a topic in the Google Groups "libflame-discuss" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/libflame-discuss/dfAn6S9ZkVU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to libflame-discuss+unsubscribe@googlegroups.com.
To post to this group, send email to libflame-discuss@googlegroups.com.
Visit this group at https://groups.google.com/group/libflame-discuss.
For more options, visit https://groups.google.com/d/optout.