-
Notifications
You must be signed in to change notification settings - Fork 284
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consistent failure when attempting to run the 'make all' command #685
Comments
What version of gcc are you using? Sounds like it's not compiling as C++11. |
Are you use the target was correctly set in Yotta? |
My gcc version is 8.1.0 and I used the following line to set the target:
|
I did think the references to C++98 were a bit strange |
Could you build with the verbose flags and copy the full output? that should show which flags were used. |
I just built on Ubuntu with gcc 7.3.1 without issues, these are the steps I take:
|
This is the build with flags: |
I followed exactly the same steps as you did for your Ubuntu build. |
This is my gcc version output:
|
Is there an issue because I have the MinGW-W64, and it says at the start of the build that "This program built for i386-pc-mingw32"? |
I don't know sorry, maybe that is just the make program build info. Based on the output though, sounds like you are building with gcc arm v5:
I'd recommend to update that. This is your x86_64 gcc:
|
Right, I'll try updating that - thanks |
The update of GCC solved my inital issue - thank you. |
I was trying out the module freezing process (shown here: https://github.com/mytechnotalent/MicroPython-micro-bit_How_To_Build_And_Freeze_Modules), but kept having issues with the 'make all' process not working.
I thought it might be the changes I was making, so cloned a fresh version of the bbcmicrobit/micropython repo and tried to build the firmware with no changes - same error. I have tried using Windows command line and the git bash environment - both consistently fail on the same section (I am using a Windows 10 machine).
This is the error message:
Is anyone able to shed light on why this fails? Are there extra steps which need to be taken before running the instructions in the README?
@dpgeorge @microbit-carlos
The text was updated successfully, but these errors were encountered: