It seems to have been another case which proves that posting about something will almost instantly have your subconscious set you on the path to revealing the answer one's been seeking.
Your pointing to that file coincided with my discovering the same and and identifying where the issue lies.
It appears it is a difference in building. This produces the link to the web page -
The Raspberry Pi recommended way of building for the RP2 doesn't -
So that seems to be where the divergence lies.
I will acknowledge the latest 'raspberry-pi-pico-python-sdk.pdf' indicates the first way for building, but I am convinced it used to indicate the second way. The second way is what's recommended for RP2 development, what I and I expect many, perhaps most, RP2 users are using, should IMO be using.
I am not going to complain about wrapping a 'cmake' build system within a 'make' build system because I can see the rationale for doing that.
It seems to me though, given MicroPython has migrated to a 'cmake' build system, that any 'web link' generation on errors must be added to 'CMakeLists.txt' or some '.cmake' or similar file, so it's provided for those using the 'cmake' build system plus those using the 'make' build wrapper around it. The 'Makefile' wrapper should be just that, a wrapper, nothing more.
jimmo wrote: ↑Sat Oct 01, 2022 1:04 pm
That's probably your (quite old!! ~2018) version of gcc, there's been lots of improvement to error messages since then.
Probably - That's the version which 'sudo apt install' gets and avoids a lot of 'you're not using a supported compiler' when issues arise on the Pi forums.