• State Suggested Answer
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 21 subscribers
  • Views 875 views
  • Users 0 members are here
Options
Related
How was your experience today?

multiple warnings when compiling a project

massimoArmDeveloper

Good morning everyone,

I'm new to this forum, so please excuse any mistakes I might make.

I recently installed the ARM GNU compiler, and since then, I've been encountering some warnings in my console during compilation. I'd like to resolve or eliminate them if possible. Can anyone offer assistance?

Here are the warnings I'm seeing:

C:/arm-gnu-toolchain-13.2.Rel1-mingw-w64-i686-arm-none-eabi/bin/../lib/gcc/arm-none-eabi/13.2.1/../../../../arm-none-eabi/bin/ld.exe: C:/arm-gnu-toolchain-13.2.Rel1-mingw-w64-i686-arm-none-eabi/bin/../lib/gcc/arm-none-eabi/13.2.1/thumb/v7e-m+fp/hard\libc_nano.a(libc_a-closer.o): in function `_close_r':
closer.c:(.text._close_r+0xc): warning: _close is not implemented and will always fail
i/bin/ld.exe: C:/arm-gnu-toolchain-13.2.Rel1-mingw-w64-i686-arm-none-eabi/bin/../lib/gcc/arm-none-eabi/13.2.1/thumb/v7e-m+fp/hard\libc_nano.a(libc_a-lseekr.o): in function `_lseek_r':
lseekr.c:(.text._lseek_r+0x10): warning: _lseek is not implemented and will always fail
C:/arm-gnu-toolchain-13.2.Rel1-mingw-w64-i686-arm-none-eabi/bin/../lib/gcc/arm-none-eabi/13.2.1/../../../../arm-none-eabi/bin/ld.exe: C:/arm-gnu-toolchain-13.2.Rel1-mingw-w64-i686-arm-none-eabi/bin/../lib/gcc/arm-none-eabi/13.2.1/thumb/v7e-readr.c:(.text._read_r+0x10): warning: _read is not implemented and will always fail
C:/arm-gnu-toolchain-13.2.Rel1-mingw-w64-i686-arm-none-eabi/bin/../lib/gcc/arm-none-eabi/13.2.1/../../../../arm-none-eabi/bin/ld.exe: C:/arm-gnu-toolchain-13.2.Rel1-mingw-w64-i686-arm-none-eabi/bin/../lib/gcc/arm-none-eabi/13.2.1/thumb/v7e-writer.c:(.text._write_r+0x10): warning: _write is not implemented and will always fail
C:/arm-gnu-toolchain-13.2.Rel1-mingw-w64-i686-arm-none-eabi/bin/../lib/gcc/arm-none-eabi/13.2.1/../../../../arm-none-eabi/bin/ld.exe: C:/arm-gnu-toolchain-13.2.Rel1-mingw-w64-i686-arm-none-eabi/bin/../lib/gcc/arm-none-eabi/13.2.1/thumb/v7e-m+fp/hard\libg_nano.a(libc_a-signalr.o): in function `_getpid_r':
signalr.c:(.text._getpid_r+0x0): warning: _getpid is not implemented and will always fail
C:/arm-gnu-toolchain-13.2.Rel1-mingw-w64-i686-arm-none-eabi/bin/../lib/gcc/arm-none-eabi/13.2.1/../../../../arm-none-eabi/bin/ld.exe: C:/arm-gnu-toolchain-13.2.Rel1-mingw-w64-i686-arm-none-eabi/bin/../lib/gcc/arm-none-eabi/13.2.1/thumb/v7e-m+fp/hard\libg_nano.a(libc_a-signalr.o): in function `_kill_r':
signalr.c:(.text._kill_r+0xe): warning: _kill is not implemented and will always fail

Could someone kindly guide me on how to address these warnings or suppress them? Any help would be greatly appreciated.

Thank you.

  • 0

    Hi Massimo

    I have moved your question to the Compilers and Libraries forum where someone may be able to help you.

    Thanks

    Oli

    Arm Community Manager

  • 0

    Hi,

    These warnings are expected if the syscall functions are not implemented by the user for re-targeting. 

    If you use --specs=nonsys.specs, then the user must re-target the syscall functions, like _close, by re-implementing them. Otherwise, a default _close function will get used, which does not have the correct implementation for re-targeting.

    If you are using semihosting, then you can use --specs=rdimon.specs.

    I hope that helps. Let us know if you have further questions.