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.
Hi
I am using MDK ARM professorial 5.38 with AC6.19. I have a pre-bulid library to integrate my project, when i compile the project with the library, the build output throw warning and error messages as below:
Warning: L6170W: Mapping symbol #30 '$t' in .bss(encode.o:21) identifies code, but is in a section not marked as executable. Warning: L6170W: Mapping symbol #32 '$t' in .bss(encode.o:22) identifies code, but is in a section not marked as executable. Warning: L6170W: Mapping symbol #34 '$t' in .bss(encode.o:23) identifies code, but is in a section not marked as executable. Warning: L6170W: Mapping symbol #36 '$t' in .bss(encode.o:24) identifies code, but is in a section not marked as executable. Warning: L6170W: Mapping symbol #38 '$t' in .bss(encode.o:25) identifies code, but is in a section not marked as executable. Warning: L6170W: Mapping symbol #40 '$t' in .bss(encode.o:26) identifies code, but is in a section not marked as executable. Warning: L6170W: Mapping symbol #42 '$t' in .bss(encode.o:27) identifies code, but is in a section not marked as executable. Warning: L6170W: Mapping symbol #44 '$t' in .bss(encode.o:28) identifies code, but is in a section not marked as executable. Warning: L6170W: Mapping symbol #46 '$t' in .bss(encode.o:29) identifies code, but is in a section not marked as executable. Error: L6405E: No .ANY selector matches encode.o(.bss). Error: L6405E: No .ANY selector matches encode.o(.bss). Error: L6405E: No .ANY selector matches encode.o(.bss). Error: L6405E: No .ANY selector matches encode.o(.bss). Error: L6405E: No .ANY selector matches encode.o(.bss). Error: L6405E: No .ANY selector matches encode.o(.bss). Error: L6405E: No .ANY selector matches encode.o(.bss).
snapshot as below:
How can i resolve this error, I have checked the arm compiler document about the "ANY selector" chapter, but i don't know about it.
Thanks very much,
From the Support menu above, select All Support Services, then Open a Support Case