Many warnings in the NRF SDK 17.1.0 when compiling with armgcc Makefile

RE: Many warnings in the NRF SDK 17.1.0 when compiling with armgcc Makefile

Yohann — Fri, 10 Dec 2021 14:48:53 GMT

Ok you're right there is something wrong on my system.

I created a blank Ubuntu Virtual machine, cloned the sdk, arm-none-eabi-gcc version 10.3.1 and it builds perfectly without any warning.

So I don't know what or where but it seems to be on my system, I'll try to find it.

Thanks you a lot for the help

RE: Many warnings in the NRF SDK 17.1.0 when compiling with armgcc Makefile

Einar Thorsrud — Fri, 10 Dec 2021 14:22:25 GMT

Yes, I am. And I am also not able to find any other reports of this issue. Do you have some system wide alias that adds some flags to GCC or something else? (I am just throwing out a guess, really...)

RE: Many warnings in the NRF SDK 17.1.0 when compiling with armgcc Makefile

Yohann — Fri, 10 Dec 2021 14:20:50 GMT

I tried with 9.3.1 and the fresh sdk and nothing changes, you're telling me that you have the exact same setup and it works for you ?

Thanks

RE: Many warnings in the NRF SDK 17.1.0 when compiling with armgcc Makefile

Einar Thorsrud — Fri, 10 Dec 2021 14:12:08 GMT

That is odd. I see you use SDK 17.1, and then 9.3.1 (which you used before) is what was used for release testing. I an using this exact combination now and the same example and I am not able to reproduce this (not even on a Mac).

RE: Many warnings in the NRF SDK 17.1.0 when compiling with armgcc Makefile

Yohann — Fri, 10 Dec 2021 14:01:27 GMT

Ok I just did that, I download a fresh version of the sdk, a fresh version of arm-none-eabi toolchain (version 10.3) and nothing changes.

What else can it be ?

RE: Many warnings in the NRF SDK 17.1.0 when compiling with armgcc Makefile

Einar Thorsrud — Fri, 10 Dec 2021 13:44:35 GMT

Hi,

The unmodified SDK example really should build without any warnings. Please unzip a fresh SDK so that we know there are no modifications and test again. If you still see this issue, I would look at your toolchain next. The OS should not be a problem. Probably not the GCC version either, but generally I recommend using the version that is mentioned in the release notes if you have issues, as that is the version that was used during release testing.

RE: Many warnings in the NRF SDK 17.1.0 when compiling with armgcc Makefile

Yohann — Fri, 10 Dec 2021 13:18:45 GMT

I don't know if this can help but I'm on MacOS big sur 11.6 and my version of arm-none-eabi-gcc is 9.3.1

RE: Many warnings in the NRF SDK 17.1.0 when compiling with armgcc Makefile

Yohann — Fri, 10 Dec 2021 13:16:13 GMT

Hello Einar,

Thanks for your quick answer, I didn't change anything about the warnings in the makefile I made except I removed -Werror because with it it's impossible to compile.

If I go in $SDK_ROOT/examples/peripheral/blinky/pca10056/blank/armgcc

which is where the Makefile of the blinky (the most basic example) is located, I didn't change anything and type 'make' it won't compile because of -Werror and the warnings.

Here is a little screenshot to show you.

RE: Many warnings in the NRF SDK 17.1.0 when compiling with armgcc Makefile

Einar Thorsrud — Fri, 10 Dec 2021 13:00:30 GMT

Hi Yohann,

I am a bit surprised about these about the error you get from SVCALL for two reasons. This is API functions in a header file and should not lead to an error like this in any case. An also, we also have unused warnings in our Makefiles in the SDK, which does not complain about this (neither should it).

Regarding the warnings you get for NRF_MODULE_ENABLED those defines should not be relevant.

I agree whole heartedly that all code should build warning free, as the opposite would easily mask warnings you really should notice. But it seems the problem here is not in the code, but rather how you build (the options you pass to GCC). I suggest you use the Makefiles in the SDK as reference, where we use both -Wall and -Werror, which should be more than strict enough.