RT-Thread / RT-Thread/rt-thread
[Bug] 关于RP2040在WIN环境下使用ENV构建报错出现bs2_default_padded_checksummed.S未找到问题
Dieses Issue hat noch niemand übernommen.
- Vorherrschende Sprache
- C
- Sterne
- 12.2k
- Forks
- 5.4k
- Ø Merge
- 4 T. 12 Std.
- Gemergte PRs (30 T.)
- 40
Beschreibung
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
Beitragsleitfaden
Erste Schritte
- Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
- Forke das Repository und arbeite in einem Branch.
- Öffne einen Pull Request, der die Issue-Nummer nennt.
Rechercherichtung
Beginne in bsp/raspberry-pico/RP2040 und prüfe packages/raspberrypi-pico-sdk-latest/SConstruct, insbesondere Zeile 65, sowie, ob bs2_default_padded_checksummed.S am referenzierten Pfad vorhanden ist. Führe scons im RP2040-Verzeichnis unter Windows erneut aus; abgeschlossen ist die Aufgabe, wenn der Build die fehlende Quelldatei nicht mehr meldet und erfolgreich abgeschlossen wird.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- c
- Bereich
- build-system, embedded-iot
- Issue-Typ
- Bug
- Schwierigkeit
- 3/5
- Geschätzter Aufwand
- 1-2 Tage
- Aktivitätsstatus
- Ruhig
- Klarheit
- Größtenteils klar
- Anfängerfreundlichkeit
- 55/100