Closed jingai closed 6 years ago
This is recently a common problem with the extensa gcc compiler. You have to use an older version of the compiler. See this discussion with links at the end: https://forum.pycom.io/topic/1429/solved-having-issues-build-firmware-from-soure
Using the correct compiler for a given firmware seems to be a recurring issue. Would adding a check / warning to the makefile be worthwhile? There are already similar checks for the esp-idf and would ensure consistent results for users which is especially important as the compiler is changing a lot.
On 11/10/2017 6:28 PM, "robert-hh" notifications@github.com wrote:
This is recently a common problem with the extensa gcc compiler. You have to use an older version of the compiler. See this discussion with links at the end: https://forum.pycom.io/topic/1429/solved-having-issues- build-firmware-from-soure
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/pycom/pycom-micropython-sigfox/issues/83#issuecomment-335687264, or mute the thread https://github.com/notifications/unsubscribe-auth/ABU_KTvKWz4cmqHTjeRvvuTdGUYnhUhkks5srFH0gaJpZM4P00ka .
@robert-hh thanks -- using specifically 1.22.0-61-gab8375a finally got it to build.
Which version of the C-Compiler are you actually using?
I managed to get it to build with 1.22.0-61-gab8375a. Thanks again.
I have pushed a new version of README.md to reflect the correct compiler version... closing this issue.
Everything compiles fine until it goes to build the image: