Skip to content
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

blinky app won't build unless upgrading to newer arm-toolchain #81

Open
manish-sudo opened this issue Sep 12, 2019 · 2 comments
Open

blinky app won't build unless upgrading to newer arm-toolchain #81

manish-sudo opened this issue Sep 12, 2019 · 2 comments

Comments

@manish-sudo
Copy link

Following instructions here if I install the 4.9 arm toolchain, and build the app, I get following error message:

$ newt create-image nrf52_blinky 1.0.0
Compiling repos/apache-mynewt-core/hw/drivers/uart/src/uart.c
Assembling repos/apache-mynewt-core/hw/bsp/nordic_pca10040/src/arch/cortex_m4/gcc_startup_nrf52.s
Assembling repos/apache-mynewt-core/hw/bsp/nordic_pca10040/src/arch/cortex_m4/gcc_startup_nrf52_split.s
Compiling repos/apache-mynewt-core/hw/bsp/nordic_pca10040/src/sbrk.c
Compiling repos/apache-mynewt-core/hw/hal/src/hal_common.c
. . .
. . .
Compiling repos/apache-mynewt-core/libc/baselibc/src/memfile.c
Compiling repos/apache-mynewt-core/libc/baselibc/src/memmem.c
Error: repos/apache-mynewt-core/kernel/os/src/os_mempool.c: In function 'os_memblock_from':
repos/apache-mynewt-core/kernel/os/src/os_mempool.c:308:5: error: implicit declaration of function 'static_assert' [-Werror=implicit-function-declaration]
static_assert(sizeof block_addr == sizeof baddr32,
^
cc1: all warnings being treated as errors

After advancing the toolchain to "version 8.2.1 20181213", the above mentioned problem was resolved. So, I think the document should be updated to avoid this issue.

@utzig
Copy link
Member

utzig commented Sep 12, 2019

I would suggest updating the docs to install whatever is latest: brew install gcc-arm-none-eabi (with no version given). It's very unlikely that a newer version of gcc will be breaking our builds, and if it does there's way more chance that we fix the broken build before we fix docs.

@manish-sudo
Copy link
Author

Makes sense!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants