-
-
Notifications
You must be signed in to change notification settings - Fork 8.2k
unknown warning option '-Wimplicit-fallthrough=0' #7546
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
Labels
Comments
This looks like a difference between gcc and clang. Probably that warning can be omitted when building with clang (eg put in the Might be a good idea to build |
dpgeorge
added a commit
to dpgeorge/micropython
that referenced
this issue
Jul 17, 2021
In 2ae3c89, -Wimplicit-fallthrough=0 was added to get the build to pass. This option is equivalent to -Wno-implicit-fallthrough, and the latter is compatible with clang (while the former is not). Fixes issue micropython#7546. Signed-off-by: Damien George <damien@micropython.org>
See #7547 for a fix, and also enabling of |
dpgeorge
added a commit
to dpgeorge/micropython
that referenced
this issue
Jul 17, 2021
In 2ae3c89, -Wimplicit-fallthrough=0 was added to get the build to pass. This option is equivalent to -Wno-implicit-fallthrough, and the latter is compatible with clang (while the former is not). Fixes issue micropython#7546. Signed-off-by: Damien George <damien@micropython.org>
Should be fixed by 74db526 |
RetiredWizard
pushed a commit
to RetiredWizard/micropython
that referenced
this issue
Feb 9, 2023
fix for native is31fl3741
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Just went to build the
dev
variant of the unix port and got this error:Building on: macOS 10.15.7 (19H1217)
From commit: 8be29b9
I modified the file
extmod/btstack/btstack.mk
to omit the offending option entirely and was able to proceed through a successful build. No warnings were generated.I understand this flag was added recently (#6578). Could this be a linux vs. osx issue?
The text was updated successfully, but these errors were encountered: