Biancaa-R commented on PR #3406:
URL: https://github.com/apache/nuttx-apps/pull/3406#issuecomment-3936041583

   > @Biancaa-R @cederom, this is the error **`flash' overflowed by 4 bytes**
   > 
   > ```
   > 
====================================================================================
   > Configuration/Tool: weact-stm32h750/nsh,CONFIG_ARM_TOOLCHAIN_CLANG
   > 2026-02-19 20:01:01
   > 
------------------------------------------------------------------------------------
   >   Cleaning...
   >   Configuring...
   >   Disabling CONFIG_ARM_TOOLCHAIN_GNU_EABI
   >   Enabling CONFIG_ARM_TOOLCHAIN_CLANG
   >   Building NuttX...
   > arm-none-eabi-ld: /github/workspace/sources/nuttx/nuttx section `.data' 
will not fit in region `flash'
   > arm-none-eabi-ld: region `flash' overflowed by 4 bytes
   > make[1]: *** [Makefile:217: nuttx] Error 1
   > make: *** [tools/Unix.mk:552: nuttx] Error 2
   > make: Target 'all' not remade because of errors.
   > /github/workspace/sources/nuttx/tools/testbuild.sh: line 385: 
/github/workspace/sources/nuttx/../nuttx/nuttx.manifest: No such file or 
directory
   >   [1/1] Normalize weact-stm32h750/nsh
   > On branch master
   > Your branch is up to date with 'origin/master'.
   > 
   > Untracked files:
   >   (use "git add <file>..." to include in what will be committed)
   >    boards/arm/stm32h7/weact-stm32h750/scripts/flash.ld.tmp
   > 
   > nothing added to commit but untracked files present (use "git add" to 
track)
   > 
====================================================================================
   > ```
   
   is // Instead of: " %04d-%02d-%02d %02d:%02d"
   nsh_output(vtbl, " %d-%d-%d", tm.tm_year + 1900, tm.tm_mon + 1, tm.tm_mday);
   better ? @simbit18 ? I think that is causing the overflow..


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