The toolchain is unable to build a dummy C file

RE: The toolchain is unable to build a dummy C file

niels.steyaert — Tue, 08 Feb 2022 13:00:29 GMT

I solved this error by deleting all the files in ..\v1.8.0\zephyr\.cache\ToolchainCapabilityDatabase

OS: Windows 10

RE: The toolchain is unable to build a dummy C file

armen — Wed, 13 Jan 2021 11:49:02 GMT

How to solve Windows 10，if I try to delete \zephyr\cache, it doesn't work

D:\blog\ncs1\version\nrf\applications\nrf_desktop>west build -bnrf52840gmouse_nrf52840 -p
-- west build: generating a build system
Including boilerplate (Zephyr base): D:/blog/ncs1/version/zephyr/cmake/app/boilerplate.cmake
-- Application: D:/blog/ncs1/version/nrf/applications/nrf_desktop
-- Using NCS Toolchain 1.4.0 for building. (D:/blog/ncs1/version/toolchain/cmake)
-- Zephyr version: 2.4.0 (D:/blog/ncs1/version/zephyr)
-- Found Python3: D:/blog/ncs1/version/toolchain/opt/bin/python.exe (found suitable exact version "3.8.2") found components: Interpreter
-- Found west (found suitable version "0.7.2", minimum required is "0.7.1")
-- Board: nrf52840gmouse_nrf52840
-- Cache files will be written to: D:/blog/ncs1/version/zephyr/.cache
-- Found dtc: D:/blog/ncs1/version/toolchain/opt/bin/dtc.exe (found suitable version "1.4.7", minimum required is "1.4.6")
-- Found toolchain: gnuarmemb (D:/blog/ncs1/version/toolchain/opt)
-- Found BOARD.dts: D:/blog/ncs1/version/nrf/boards/arm/nrf52840gmouse_nrf52840/nrf52840gmouse_nrf52840.dts
-- Found devicetree overlay: D:/blog/ncs1/version/nrf/applications/nrf_desktop/configuration/nrf52840gmouse_nrf52840/dts.overlay
-- Generated zephyr.dts: D:/blog/ncs1/version/nrf/applications/nrf_desktop/build/zephyr/zephyr.dts
-- Generated devicetree_unfixed.h: D:/blog/ncs1/version/nrf/applications/nrf_desktop/build/zephyr/include/generated/devicetree_unfixed.h
Parsing D:/blog/ncs1/version/nrf/applications/nrf_desktop/Kconfig
Loaded configuration 'D:/blog/ncs1/version/nrf/boards/arm/nrf52840gmouse_nrf52840/nrf52840gmouse_nrf52840_defconfig'
Merged configuration 'configuration/nrf52840gmouse_nrf52840/app_ZDebug.conf'
Configuration saved to 'D:/blog/ncs1/version/nrf/applications/nrf_desktop/build/zephyr/.config'
Kconfig header saved to 'D:/blog/ncs1/version/nrf/applications/nrf_desktop/build/zephyr/include/generated/autoconf.h'
-- The C compiler identification is GNU 9.2.1
-- The CXX compiler identification is GNU 9.2.1
-- The ASM compiler identification is GNU
-- Found assembler: D:/blog/ncs1/version/toolchain/opt/bin/arm-none-eabi-gcc.exe
CMake Error at D:/blog/ncs1/version/zephyr/cmake/extensions.cmake:1557 (message):
Assertion failed: The toolchain is unable to build a dummy C file. See
CMakeError.log.
Call Stack (most recent call first):
D:/blog/ncs1/version/zephyr/CMakeLists.txt:42 (assert)

which says in the error of the CMakeError.log that

Compiling the C compiler identification source file "CMakeCCompilerId.c" failed.
Compiler: D:/blog/ncs1/version/toolchain/opt/bin/arm-none-eabi-gcc.exe
Build flags:
Id flags:

The output was:
1
d:/blog/ncs1/version/toolchain/opt/bin/../lib/gcc/arm-none-eabi/9.2.1/../../../../arm-none-eabi/bin/ld.exe: d:/blog/ncs1/version/toolchain/opt/bin/../lib/gcc/arm-none-eabi/9.2.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: D:/blog/ncs1/version/toolchain/opt/bin/arm-none-eabi-gcc.exe
Build flags:
Id flags:

RE: The toolchain is unable to build a dummy C file

mraposo1 — Wed, 14 Oct 2020 23:12:38 GMT

Also, on Windows, where are the library caches?

RE: The toolchain is unable to build a dummy C file

mraposo1 — Wed, 14 Oct 2020 23:11:26 GMT

Could you define "wherever the toolchain is defined" better, please?

RE: The toolchain is unable to build a dummy C file

Sven — Fri, 13 Dec 2019 18:20:55 GMT

Super, it works! Is that the ccache configure folder there?

RE: The toolchain is unable to build a dummy C file

Einar Thorsrud — Fri, 13 Dec 2019 12:40:02 GMT

Hi,

Most example projects should build-out of the box when the toolchain is installed correctly. However, one thing that could potentially be a problem here is the Cmake cache. Can you try to delete ~/Library/Caches/zephyr before building and see if that helps?

RE: The toolchain is unable to build a dummy C file

Sven — Thu, 12 Dec 2019 18:22:50 GMT

Yup. First in modern CMake one should operate on target bases, not on some set({global}), so I should prefer that way, would need to learn the CMake tree in zypher projects anyway with both approaches. Second, why is this happening to my setup, since this is a dummy compilation it should happen with every board, so I believe it should not be anything specific to nRF53.

RE: The toolchain is unable to build a dummy C file

Benjamin — Wed, 11 Dec 2019 22:20:30 GMT

You can also add the following line to wherever the toolchain is defined:

# Perform compiler test without linker, since we're cross-compiling
set(CMAKE_TRY_COMPILE_TARGET_TYPE STATIC_LIBRARY)

RE: The toolchain is unable to build a dummy C file

Sven — Wed, 11 Dec 2019 19:43:51 GMT

So --specs=nosys.specs works.

I tried to do a dummy linking manually inside the build/CMakeFiles/3.14.5/CompilerIdC directory.

➜ CompilerIdC git:(b687d5d022) ✗ pwd
.../ncs/zephyr/samples/bluetooth/hci_rpmsg/build/CMakeFiles/3.14.5/CompilerIdC
➜ CompilerIdC git:(b687d5d022) ✗ ll
total 48
-rw-r--r-- 1 svenkautlenbach staff 20K Dec 11 21:24 CMakeCCompilerId.c
-rw-r--r-- 1 svenkautlenbach staff 1.6K Dec 11 21:24 CMakeCCompilerId.o
drwxr-xr-x 2 svenkautlenbach staff 64B Dec 11 21:24 tmp
➜ CompilerIdC git:(b687d5d022) ✗ arm-none-eabi-gcc -o tere CMakeCCompilerId.c
/Users/svenkautlenbach/gnuarmemb/bin/../lib/gcc/arm-none-eabi/8.3.1/../../../../arm-none-eabi/bin/ld: /Users/svenkautlenbach/gnuarmemb/bin/../lib/gcc/arm-none-eabi/8.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: error: ld returned 1 exit status
➜ CompilerIdC git:(b687d5d022) ✗ arm-none-eabi-gcc --specs=nosys.specs -o tere CMakeCCompilerId.c
➜ CompilerIdC git:(b687d5d022) ✗

So am I missing something important in build system or should I modify build system files then ?