RT-Thread / RT-Thread/rt-thread
[Bug] 关于RP2040在WIN环境下使用ENV构建报错出现bs2_default_padded_checksummed.S未找到问题
Personne n'a encore pris cette issue.
- Langage dominant
- C
- Étoiles
- 12.2k
- Forks
- 5.4k
- Merge moyen
- 4 j 12 h
- PR mergées (30 j)
- 40
Description
RT-Thread Version
master
Hardware Type/Architectures
RP2040
Develop Toolchain
Other
Describe the bug
(.venv) @DESKTOP-S0GUQ6A E:\RT-ThreadEnv\rt-thread\bsp\raspberry-pico\RP2040
$ scons
scons: Reading SConscript files ...
Newlib version: 4.1.0
Enter E:\RT-ThreadEnv\rt-thread\bsp\raspberry-pico\RP2040\packages\raspberrypi-pico-sdk-latest
scons: Reading SConscript files ...
scons: *** An executable should have exactly one target with the suffix: .exe
File "E:\RT-ThreadEnv\rt-thread\bsp\raspberry-pico\RP2040\packages\raspberrypi-pico-sdk-latest\SConstruct", line 65, in
scons: done reading SConscript files.
scons: Building targets ...
scons: building associated VariantDir targets: build
CC build\applications\main.o
CC build\board\board.o
CC build\kernel\components\drivers\core\device.o
CC build\kernel\components\drivers\ipc\completion_comm.o
CC build\kernel\components\drivers\ipc\completion_up.o
CC build\kernel\components\drivers\ipc\condvar.o
CC build\kernel\components\drivers\ipc\dataqueue.o
CC build\kernel\components\drivers\ipc\pipe.o
CC build\kernel\components\drivers\ipc\ringblk_buf.o
CC build\kernel\components\drivers\ipc\ringbuffer.o
CC build\kernel\components\drivers\ipc\waitqueue.o
CC build\kernel\components\drivers\ipc\workqueue.o
CC build\kernel\components\drivers\pin\dev_pin.o
CC build\kernel\components\drivers\serial\dev_serial.o
CC build\kernel\components\drivers\spi\dev_spi.o
CC build\kernel\components\drivers\spi\dev_spi_core.o
CC build\kernel\components\finsh\cmd.o
CC build\kernel\components\finsh\msh.o
CC build\kernel\components\finsh\msh_parse.o
CC build\kernel\components\finsh\shell.o
CC build\kernel\components\libc\compilers\common\cctype.o
CC build\kernel\components\libc\compilers\common\cstdlib.o
CC build\kernel\components\libc\compilers\common\cstring.o
CC build\kernel\components\libc\compilers\common\ctime.o
CC build\kernel\components\libc\compilers\common\cunistd.o
CC build\kernel\components\libc\compilers\common\cwchar.o
CC build\kernel\components\libc\compilers\newlib\syscalls.o
CC build\kernel\libcpu\arm\common\div0.o
CC build\kernel\libcpu\arm\common\showmem.o
CC build\kernel\src\clock.o
CC build\kernel\src\components.o
CC build\kernel\src\cpu_up.o
CC build\kernel\src\defunct.o
CC build\kernel\src\idle.o
CC build\kernel\src\ipc.o
CC build\kernel\src\irq.o
CC build\kernel\src\klibc\kerrno.o
CC build\kernel\src\klibc\kstdio.o
CC build\kernel\src\klibc\kstring.o
CC build\kernel\src\klibc\rt_vsnprintf_tiny.o
CC build\kernel\src\klibc\rt_vsscanf.o
CC build\kernel\src\kservice.o
CC build\kernel\src\mem.o
CC build\kernel\src\mempool.o
CC build\kernel\src\object.o
CC build\kernel\src\scheduler_comm.o
CC build\kernel\src\scheduler_up.o
CC build\kernel\src\thread.o
CC build\kernel\src\timer.o
AS build\libcpu\context_gcc.o
CC build\libcpu\cpuport.o
scons: *** [build\packages\raspberrypi-pico-sdk-latest\bs2_default_padded_checksummed.o] **Source packages\raspberrypi-pico-sdk-latest\bs2_default_padded_checksummed.S' not found,** needed by target build\packages\raspberrypi-pico-sdk-latest\bs2_default_padded_checksummed.o'.
scons: building terminated because of errors.
Other additional context
No response
Guide de contribution
Ouvrir le guide de contribution
Par où commencer
- Lisez l'issue en entier, puis le guide de contribution du projet.
- Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
- Forkez le dépôt et travaillez sur une branche.
- Ouvrez une pull request qui référence le numéro de l'issue.
Piste de recherche
Commencez dans bsp/raspberry-pico/RP2040 et inspectez packages/raspberrypi-pico-sdk-latest/SConstruct, en particulier la ligne 65, ainsi que l’existence de bs2_default_padded_checksummed.S à l’emplacement référencé. Relancez scons dans le répertoire RP2040 sous Windows ; c’est terminé lorsque le build ne signale plus l’absence du fichier source et se termine avec succès.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- c
- Domaine
- build-system, embedded-iot
- Type d'issue
- Bug
- Difficulté
- 3/5
- Temps estimé
- 1-2 jours
- Activité
- Calme
- Clarté
- Plutôt claire
- Accessibilité débutants
- 55/100