micro-ROS / micro-ROS/micro_ros_stm32cubemx_utils
Get Error and warning ...(.text._gettimeofday_r+0xe): warning: _gettimeofday is not implemented and will always fail
- Dominant language
- C
- Stars
- 275
- Forks
- 100
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
I Get this error:
/home/shahrol/st/stm32cubeide_1.11.0_6/plugins/com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.11.3.rel1.linux64_1.1.0.202305231506/tools/bin/../lib/gcc/arm-none-eabi/11.3.1/../../../../arm-none-eabi/bin/ld: /home/shahrol/st/stm32cubeide_1.11.0_6/plugins/com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.11.3.rel1.linux64_1.1.0.202305231506/tools/bin/../lib/gcc/arm-none-eabi/11.3.1/../../../../arm-none-eabi/lib/thumb/v7e-m+fp/hard/libc_nano.a(libc_a-gettimeofdayr.o): in function `_gettimeofday_r':
(.text._gettimeofday_r+0xe): warning: _gettimeofday is not implemented and will always fail
when I upgrade the STM32CubeIde from version 1.11.0 to 1.13.0. I figure out this error is generate when I init the rclc_executor...rclc_executor_init(&main_executor, &support.context, 5, &allocator);
How to resolve this error
Contributor guide
Research direction
Start by reproducing the warning after upgrading STM32CubeIDE from 1.11.0 to 1.13.0, then inspect the build and linker output around the reported _gettimeofday_r warning. Compare the behavior with and without rclc_executor_init(&main_executor, &support.context, 5, &allocator). Done means identifying a supported configuration or change that removes the warning.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- embedded-iot
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100