simbit18 commented on PR #17142:
URL: https://github.com/apache/nuttx/pull/17142#issuecomment-3356071976

   This error is caused by an incorrect defconfig.
   ```
   
==================================================================================
   ==
   Configuration/Tool: raspberrypi-pico/lcd1602,CONFIG_ARM_TOOLCHAIN_GNU_EABI
   2025-10-01 10:56:59
   
------------------------------------------------------------------------------------
     Cleaning...
     Configuring...
     Disabling CONFIG_ARM_TOOLCHAIN_GNU_EABI
     Enabling CONFIG_ARM_TOOLCHAIN_GNU_EABI
     Building NuttX...
   
/tools/gcc-arm-none-eabi/bin/../lib/gcc/arm-none-eabi/13.2.1/../../../../arm-none-eabi/bin/ld:
 cannot open linker script file 
/github/workspace/sources/nuttx/boards/arm/rp2040/raspberrypi-pico-w/scripts/raspberrypi-pico-flash.ld:
 No such file or directory
   collect2: error: ld returned 1 exit status
   make[2]: *** [chip/boot2/Make.defs:58: rp2040_boot_stage2.elf] Error 1
   make[2]: Target 'makedepfile' not remade because of errors.
   make[1]: *** [Makefile:261: .depend] Error 2
   make[1]: Target 'depend' not remade because of errors.
   make: *** [tools/Unix.mk:660: pass2dep] 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 raspberrypi-pico/lcd1602
   
====================================================================================
   ```
   
   This PR #6850 modified the correct defconfig.
   
https://github.com/apache/nuttx/commit/74f1bfbfd7d578ba74f1885548a8be0901df0c34#diff-7adf2962c264c6593cfb678b993cf724ca09900859c26caea0f1be664d261014
   
   I will add a fix


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