-
-
Notifications
You must be signed in to change notification settings - Fork 559
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
Problems compiling 1.4.1 on MacOS using multiple versions of gcc-arm-none-eabi #420
Comments
Forgot to include....
And
|
Hello are you compiling with gcc version 10 ? |
I tried to compile with version 9.3.1 , version 10.2.1, and version 10.3.1. |
Hi , and when you tried to compile , 9.3.1 , you also followed all the listed steps , (https://github.com/eried/portapack-mayhem/wiki/Compile-firmware), including that one :
sed -i 's/env python/env python3/g' /opt/portapack-mayhem/hackrf/firmware/libopencm3/scripts/irq2nvic_h |
Don't think that will change anything, since I'm on MacOS and not Debian, and that...
But, I'm game to try...
Different failure this time...
|
Hi, now, as you said , different compiler errors, getting closer ! In my case, I am also not using Debian (same as you) , but eventhough , I am using Gentoo distro and it is also linux , therefore, I followed all the steps that I need.. basically from the (3) onwards, checking carefully one by one ,if they had sense or not, and if the directory path folders were exactly the same or not ... And eventually I am compiling it with gcc-10.2.0 very fast , withouth any problems. (just adding and merging my commented PR) Then same advise , pls follow previous Mayhem compile wiki guide , and I hope and believe that you should be able to compile Mayhem with gcc 9 without any error . (even some warnings, that you can ignore ) . If not , we should better ask additional help , from other more advanced linux Mac user help . |
Okay, this was strange (but it's working now!)... On my Mac, the 'git status' showed that I was in sync and had no "dangling bits". BUT, there was some dangling cmake history cruft somewhere since I was compiling with "gcc-arm-none-eabi-9-2020-q2-update" but the error was it was trying to include things from "gcc-arm-none-eabi-9-2019-q4-major"... So, this was the working sequence to compile on MacOS using gcc-arm-none-eabi-9-2020-q2-update for me...
Still can't compile with gcc-arm-none-eabi-10.3-2021.10 though. But, did not expect it to, based on Brumi's comments/PR. |
Describe the bug
Getting errors when compiling 1.4.1 on same system/compiler that worked with 1.4.0...
To Reproduce
Steps to reproduce the behavior:
Expected behavior
It compiles? :)
Additional write with output of three different compiles using three different version of the compiler
On my iMac using gcc-arm-none-eabi-9-2020-q2-update and cmake version 3.21.4 on MacOS 11.6, which previously compiled 1.4.0 correctly I pulled the updates to the repo and did a rebuild and got this error...
That's weird, missing stdint.h? Maybe I should use a newer update of the compiler, so let's download and try again using gcc-arm-none-eabi-10-2020-q4-major and cmake version 3.21.4 on MacOS 11.6...
Okay, that's a different error than missing stdint.h. Hmmm, maybe I should use the absolute latest update, so download and try using gcc-arm-none-eabi-10.3-2021.10 and cmake version 3.21.4 on MacOS 11.6...
Same compile error as previously. Any suggestions on where to start?
The text was updated successfully, but these errors were encountered: