xiaoxiang781216 opened a new pull request, #21866:
URL: https://github.com/apache/nuttx/pull/21866

   ## Summary
   
   * Work around the current Clang build failure in the ARM NXP CI job.
   * Switch the `/arm/lpc54xx` test-list entry from Clang to GNU EABI; restore 
Clang after the underlying build issue is fixed.
   * Related NuttX PR: #21862 (CI failure context). Related NuttX Apps 
issue/PR: None.
   
   ## Impact
   
   * Existing CI compiler selection changed: YES, for `/arm/lpc54xx` only.
   * User impact: NO.
   * Build impact: YES, the CI build uses GNU EABI instead of Clang for this 
test-list entry.
   * Hardware impact: NO.
   * Documentation update: NO.
   * Security impact: NO.
   * Compatibility impact: NO.
   * Other: CI coverage only; no OS runtime behavior changes.
   
   ## Testing
   
   * Host: Linux 6.18.33.2-microsoft-standard-WSL2, x86_64; arm-none-eabi-gcc 
13.2.1.
   * Before: [Linux (arm-nxp) `Run builds` 
failed](https://github.com/apache/nuttx/actions/runs/43711076376/job/132802950121).
   * After: `tools/testbuild.sh` passed for 
`lpcxpresso-lpc54628:pwfb,CONFIG_ARM_TOOLCHAIN_GNU_EABI`:
   
     ```
     Configuration/Tool: lpcxpresso-lpc54628:pwfb,CONFIG_ARM_TOOLCHAIN_GNU_EABI
     Building NuttX...
     [1/1] Normalize lpcxpresso-lpc54628:pwfb
     nuttx: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), statically 
linked, with debug_info, not stripped
     ```
   
   * Other LPC54xx configurations and on-device runtime were not tested.
   
   ## PR verification Self-Check
   
   * [x] This PR introduces only one functional change.
   * [x] I have updated all required description fields above.
   * [x] My PR adheres to Contributing Guidelines and Documentation.
   * [ ] My PR is still work in progress.
   * [x] My PR is ready for review and can be safely merged into a codebase.
   


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