This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

SES did not finish cmake in sample http_application_update

Hi

I am trying to install the SES toolchain on my PC (Win 8.1) following exactly the nRF Connect v3.2.0 Getting Started Assistant. When trying to "Open nRF Connect Project..." into SES 4.20a I get the following prompt:

CMakeError.log

Compiling the C compiler identification source file "CMakeCCompilerId.c" failed.
Compiler: C:/work/gnuarmemb/bin/arm-none-eabi-gcc.exe 
Build flags: 
Id flags:  

The output was:
1
c:/work/gnuarmemb/bin/../lib/gcc/arm-none-eabi/7.3.1/../../../../arm-none-eabi/lib\libc.a(lib_a-exit.o): In function `exit':
exit.c:(.text.exit+0x2c): undefined reference to `_exit'
collect2.exe: error: ld returned 1 exit status


Compiling the CXX compiler identification source file "CMakeCXXCompilerId.cpp" failed.
Compiler: C:/work/gnuarmemb/bin/arm-none-eabi-gcc.exe 
Build flags: 
Id flags:  

The output was:
1
c:/work/gnuarmemb/bin/../lib/gcc/arm-none-eabi/7.3.1/../../../../arm-none-eabi/lib\libc.a(lib_a-exit.o): In function `exit':
exit.c:(.text.exit+0x2c): undefined reference to `_exit'
collect2.exe: error: ld returned 1 exit status

CMakeOutput.log

The target system is: Generic - 1.14.99 - arm
The host system is: Windows - 6.3.9600 - AMD64
Compiling the C compiler identification source file "CMakeCCompilerId.c" succeeded.
Compiler: C:/work/gnuarmemb/bin/arm-none-eabi-gcc.exe 
Build flags: 
Id flags: -c 

The output was:
0


Compilation of the C compiler identification source "CMakeCCompilerId.c" produced "CMakeCCompilerId.o"

The C compiler identification is GNU, found in "C:/work/git/ncs/nrf/samples/nrf9160/http_application_update/build_nrf9160_pca10090ns/CMakeFiles/3.15.2/CompilerIdC/CMakeCCompilerId.o"

Compiling the CXX compiler identification source file "CMakeCXXCompilerId.cpp" succeeded.
Compiler: C:/work/gnuarmemb/bin/arm-none-eabi-gcc.exe 
Build flags: 
Id flags: -c 

The output was:
0


Compilation of the CXX compiler identification source "CMakeCXXCompilerId.cpp" produced "CMakeCXXCompilerId.o"

The CXX compiler identification is GNU, found in "C:/work/git/ncs/nrf/samples/nrf9160/http_application_update/build_nrf9160_pca10090ns/CMakeFiles/3.15.2/CompilerIdCXX/CMakeCXXCompilerId.o"

Checking whether the ASM compiler is GNU using "--version" matched "(GNU assembler)|(GCC)|(Free Software Foundation)":
arm-none-eabi-gcc.exe (GNU Tools for Arm Embedded Processors 7-2018-q2-update) 7.3.1 20180622 (release) [ARM/embedded-7-branch revision 261907]
Copyright (C) 2017 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Performing C SOURCE FILE Test toolchain_is_ok succeeded with the following output:
Change Dir: C:/work/git/ncs/nrf/samples/nrf9160/http_application_update/build_nrf9160_pca10090ns/CMakeFiles/CMakeTmp

Run Build Command(s):C:/ProgramData/chocolatey/bin/ninja.exe cmTC_c7f85 && [1/2] Building C object CMakeFiles/cmTC_c7f85.dir/src.c.obj

[2/2] Linking C executable cmTC_c7f85

c:/work/gnuarmemb/bin/../lib/gcc/arm-none-eabi/7.3.1/../../../../arm-none-eabi/bin/ld.exe: warning: cannot find entry symbol _start; defaulting to 00008000



Source file was:
int main(void) { return 0; }

There is no other output in SES Console.

The strange thing is, that the other samples such as lte_ble_gateway or asset_tracker build without problem with exactly the same setup.

I checked out tag v1.0.0 from the nrf github repo and I'm using cmake version 3.15.2 and west v0.6.2.

What is wrong with my setup or with this sample? I am stuck here.

BR, Marc

Parents
  • Hi,

    The error-code itself seems to be the same as in this post.

    Did you build for nrf9160_pca10090ns or nrf9160_pca10090?

    Do you have any old build folders in the http_application_update folder? If yes, could you try to delete them ?

  • Hi Sigurd

    Thx for your reply! Yes,I have built it for nrf9160_pca10090ns (see screenshot below) and deleted the build folder previously resulting in the same error.

    However I found now a solution. After the first try with the "cmake did not finish" error, I ran the "Open nRF Connect Project.." a second time without deleting the build folder and without ticking the "Clear Build Directory" then the build of the project worked just fine! Now I can not reproduce the "cmake did not finish" error anymore. I don't understand what happend. Does CMake or SES cache some data somewhere else that messed it all up?

    BR

    Marc

Reply
  • Hi Sigurd

    Thx for your reply! Yes,I have built it for nrf9160_pca10090ns (see screenshot below) and deleted the build folder previously resulting in the same error.

    However I found now a solution. After the first try with the "cmake did not finish" error, I ran the "Open nRF Connect Project.." a second time without deleting the build folder and without ticking the "Clear Build Directory" then the build of the project worked just fine! Now I can not reproduce the "cmake did not finish" error anymore. I don't understand what happend. Does CMake or SES cache some data somewhere else that messed it all up?

    BR

    Marc

Children
Related