RT-Thread / RT-Thread/rt-thread

[新手任务][BSP] 编译错误

Open
#7,764 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

good first issue
Dominant language
C
Stars
12.2k
Forks
5.4k
Avg merge
4d 12h
Merged PRs (30d)
40

Description

目录下面执行命令scons 编译错误

❌ build nuvoton/numaker-hmi-ma35d1 failed.
❌ build nuvoton/numaker-m467hj failed.
❌ build nuvoton/numaker-m2354 failed.
❌ build nuvoton/ma35-rtp failed.
❌ build nuvoton/numaker-pfm-m487 failed.
❌ build nuvoton/nk-rtu980 failed.
❌ build nuvoton/nk-980iot failed.
❌ build nuvoton/numaker-m032ki failed.
❌ build nuvoton/nk-n9h30 failed.
❌ build nuvoton/numaker-iot-ma35d1 failed.
❌ build nuvoton/numaker-iot-m467 failed.
❌ build nuvoton/numaker-iot-m487 failed.
❌ build ft2004 failed.
❌ build yichip/yc3121-pos failed.
❌ build hc32l136 failed.
❌ build airm2m/air105 failed.
❌ build mm32l07x failed.
❌ build w60x failed.
❌ build apm32/apm32f030r8-miniboard failed.
❌ build apm32/apm32f051r8-evalboard failed.
❌ build nxp/lpc/lpc54114-lite failed.
❌ build nxp/lpc/lpc5410x failed.
❌ build nxp/lpc/lpc54608-LPCXpresso failed.
❌ build nxp/imx/imx6ull-smart failed.
❌ build raspberry-pi/raspi2 failed.
❌ build essemi/es32f0654 failed.
❌ build essemi/es32f365x failed.
❌ build ti/c28x/tms320f28379d failed.
❌ build wch/arm/ch579m failed.
❌ build microchip/saml10 failed.
❌ build ht32/ht32f52352 failed.
❌ build ht32/ht32f12366 failed.
❌ build fm33lc026 failed.
❌ build amebaz failed.

参考log
https://github.com/supperthomas/rt-thread/actions/runs/10545116916/job/29214908468

https://productionresultssa6.blob.core.windows.net/actions-results/98d6efa6-ed8b-4a69-b1b2-4048c56890e3/workflow-job-run-ca395085-040a-526b-2ce8-bdc85f692774/logs/job/job-logs.txt?rsct=text%2Fplain&se=2024-08-25T09%3A26%3A30Z&sig=10qMyQeoSUj8j2tAU7N92j1oBOYqwfajJDbicoQs0Tk%3D&ske=2024-08-25T17%3A40%3A02Z&skoid=ca7593d4-ee42-46cd-af88-8b886a2f84eb&sks=b&skt=2024-08-25T05%3A40%3A02Z&sktid=398a6654-997b-47e9-b12b-9515b896b4de&skv=2024-05-04&sp=r&spr=https&sr=b&st=2024-08-25T09%3A16%3A25Z&sv=2024-05-04

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by running scons in the repository and inspect the linked GitHub Actions run and job log to identify the first concrete compiler error. The issue lists many failing BSP targets but no source file or diagnostic. Done means the affected targets build successfully and the relevant workflow passes.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
build-system, ci-cd, embedded-iot
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.