acassis commented on PR #14197:
URL: https://github.com/apache/nuttx/pull/14197#issuecomment-2429309745

   @xiaoxiang781216 @lupyuen what are these errors:
   
   ```
   Cmake in present: nucleo-f722ze/cansock,CONFIG_ARM_TOOLCHAIN_CLANG
   Configuration/Tool: nucleo-f722ze/cansock,CONFIG_ARM_TOOLCHAIN_CLANG
   2024-10-21 23:03:46
   
------------------------------------------------------------------------------------
     Cleaning...
     Configuring...
     Select HOST_LINUX=y
   CMake Error at cmake/nuttx_add_library.cmake:136 (add_library):
     Cannot find source file:
   
       
/github/workspace/sources/nuttx/boards/arm/stm32f7/common/src/stm32_cansock.c
   Call Stack (most recent call first):
     boards/CMakeLists.txt:34 (nuttx_add_kernel_library)
   
   
   CMake Generate step failed.  Build files cannot be regenerated correctly.
   -- Configuring done (0.3s)
   CMake Error at cmake/nuttx_add_library.cmake:136 (add_library):
     Cannot find source file:
   
       
/github/workspace/sources/nuttx/boards/arm/stm32f7/common/src/stm32_cansock.c
   Call Stack (most recent call first):
     boards/CMakeLists.txt:34 (nuttx_add_kernel_library)
   
   
   -- Generating done (0.2s)
   CMake Generate step failed.  Build files cannot be regenerated correctly.
     Disabling CONFIG_ARM_TOOLCHAIN_GNU_EABI
     Enabling CONFIG_ARM_TOOLCHAIN_CLANG
     Building NuttX...
   ninja: error: loading 'build.ninja': No such file or directory
   ninja: error: loading 'build.ninja': No such file or directory
   cp: cannot stat 'nuttx.bin': No such file or directory
   cp: cannot stat 'nuttx.bin': No such file or directory
   ninja: error: loading 'build.ninja': No such file or directory
   ninja: error: loading 'build.ninja': No such file or directory
   ```


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to