Problem building application using NCS

[GiulianoFranchetto]

Hi,

I can't build any samples anymore for my nrf9160-DK using neither SES nor CLI only.

I followed the "Getting started assistant", pulled the v0.4.0 version of the SDK, west update'd everything. I also checked that I have the correct gnuarmemb version "7-2018-q2-update".

However, when I build either a sample or one of my program, le linker fails with the following error:

[ 95%] Built target linker_pass_final_script_target
[ 96%] Generating isr_tables.c
/usr/bin/objcopy:/home/giulianofranchetto/Desktop/embedded-m3/lib/fake_project/build/zephyr/zephyr_prebuilt.elf: Invalid bfd target
zephyr/CMakeFiles/zephyr_final.dir/build.make:61: recipe for target 'zephyr/isr_tables.c' failed
make[2]: *** [zephyr/isr_tables.c] Error 1
CMakeFiles/Makefile2:426: recipe for target 'zephyr/CMakeFiles/zephyr_final.dir/all' failed
make[1]: *** [zephyr/CMakeFiles/zephyr_final.dir/all] Error 2
Makefile:83: recipe for target 'all' failed

What am I missing? Should I rolled everything back to v0.3.0?

Regards

Giuliano

[MJD093]

Question, when you updated to 0.4.0, did you delete the build folder and make a new one where you re-ran the 'cmake -GNinja -DBOARD=nrf9160_pca10090ns ..' command or just re-ran cmake in the existing build folder?

[GiulianoFranchetto]

Hi,

I've cleaned everything up (the build folder + the cmake temp files).

[MJD093]

Strange, I know when I updated to the latest latest build it also broke my build command. Checking out to 0.4.0 and remaking my build folders resolved the issue for me. Just checking but your folder structure for NCS is the same as layed out in the 'getting started' info? Your build is getting to 96% so it must be finding most of the build files.

[GiulianoFranchetto]

The folder structure is indeed the same as in the getting started.

I also tried to build a "typical" zephyr program (without NCS), and the build fails with the same error! Was something broken in a gnuarmemb update, or an ubuntu package?

[GiulianoFranchetto]

The issue has been fixed on slack. On my env variable was all messed up. A quick logout and everything is working fine now!

Sorry for non-problem