mehrdadh commented on issue #8595:
URL: https://github.com/apache/tvm/issues/8595#issuecomment-893817448


   Follow up issues that should be fixed:
   - The latest fix on this PR breaks on NRF board which seems to be because of 
`prj.conf` misconfiguration.
   - stm32l4r5zi_nucleo is removed from the hardware target list.
   - It also fails on disco board with similar error to NRF:
   ```
   may be incomplete.
   
   make[2]: warning:  Clock skew detected.  Your build may be incomplete.
   
   make[2]: Warning: File 'zephyr/CMakeFiles/zephyr_prebuilt.dir/depend.make' 
has modification time 0.4 s in the future
   
   
/home/vagrant/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/10.2.0/../../../../arm-zephyr-eabi/bin/ld:
 ../app/libapp.a(main.c.obj): in function `sys_rand32_get':
   
   
/home/mhessar/jenkins-cpu/workspace/exec_0/microtvm-build/3rdparty/tvm/tests/micro/zephyr/workspace_test_zephyr_stm32f746g_disco/2021-08-05T19-25-00/project/build/zephyr/include/generated/syscalls/rand32.h:33:
 undefined reference to `z_impl_sys_rand32_get'
   
   
/home/vagrant/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/10.2.0/../../../../arm-zephyr-eabi/bin/ld:
 
/home/mhessar/jenkins-cpu/workspace/exec_0/microtvm-build/3rdparty/tvm/tests/micro/zephyr/workspace_test_zephyr_stm32f746g_disco/2021-08-05T19-25-00/project/build/zephyr/include/generated/syscalls/rand32.h:33:
 undefined reference to `z_impl_sys_rand32_get'
   
   collect2: error: ld returned 1 exit status
   
   make[2]: *** [zephyr/zephyr_prebuilt.elf] Error 1
   
   make[1]: *** [zephyr/CMakeFiles/zephyr_prebuilt.dir/all] Error 2
   
   make: *** [all] Error 2
   
   ------------------------------ Captured log call ------------------------
   
   @areusch @gromero 
   ```


-- 
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