Update CI Linux Docker file to use latest GNU and Clang toolchains #17849

Barto22 · 2026-01-13T06:45:03Z

This commit updates the Linux CI Docker image to the latest GNU and Clang toolchains. This PR is related to: #17826

Summary

This change updates the GNU (gcc/g++) and Clang (clang/clang++) toolchains used by the Linux CI Docker image to their latest stable versions.
The motivation is to ensure CI builds track supported compilers, improve warning coverage, and detect issues earlier during development.
The update includes minor adjustments to package names and installation scripts to align with distribution changes.

Impact

CI builds will use newer compilers with expanded warnings and better C/C++23 support.
No impact on downstream users unless they explicitly rely on CI-provided compiler versions.
No functional changes to runtime behavior or board configurations.
Improves compatibility with modern host toolchains and prevents bit-rot for newer distributions.
No documentation changes needed.

Testing

CI pipeline was executed across standard Linux configurations. The following was verified:

Full NuttX build matrix completed without regressions.
GCC and Clang builds both succeeded for representative board targets.
ostest and common example applications executed successfully within CI environment (logs available in CI artifacts).

Host: GitHub Actions CI (Ubuntu Linux)
Boards tested in CI: sim, nsh, plus standard matrix defaults.

No build regressions observed.

This commit will update Linux Docker to latest GNU and Clang toolchains. Signed-off-by: Bartosz <bartol2205@gmail.com>

simbit18 · 2026-01-13T11:39:06Z

Question for @Barto22 and everyone:

Does this bump resolve the known issues?

#16896

Before proceeding with the merge, I would recommend testing the new Nuttx Docker image by compiling all <board name>:<board configuration>.

We also need to check the toolchain update for the other operating systems (macOS and Windows - MSYS2/Native) present in the CI, so that the update does not leave anyone behind.

Otherwise, there is a risk that all attention will be focused on one OS at the expense of others.

For example macOS issues on NuttX Mirror
#17818

I remind myself and everyone else:

The Inviolable Principles of NuttX
https://nuttx.apache.org/docs/latest/introduction/inviolables.html#all-users-matter

lupyuen

@Barto22 Do you have Build Logs of the updated Docker Image, compiling the various NuttX Targets? Thanks!

lupyuen · 2026-01-13T11:52:19Z

@Barto22: Here are the steps for building and testing an updated Dockerfile for NuttX

https://lupyuen.org/articles/pr#appendix-downloading-the-docker-image-for-nuttx-ci

Barto22 · 2026-01-13T12:18:44Z

@Barto22 Do you have Build Logs of the updated Docker Image, compiling the various NuttX Targets? Thanks!

I will test it and provide logs.

Barto22 · 2026-01-13T19:36:43Z

@Barto22 Do you have Build Logs of the updated Docker Image, compiling the various NuttX Targets? Thanks!

I will test it and provide logs.

Currently I'm testing builds, docker image build successfully, I will test all configurations, I see that on gcc 15 there is a problem with libcxx, my PR #17826 fix it because it switches to latest LLVM libcxx and libcxxabi but before we merge it I will try to repair it here.

cederom · 2026-01-13T21:35:23Z

Thank you @Barto22 :-) You may want to replicate our CI build process for Linux too that could be best benchmark for comparison :-)

If that works fine locally and here on github then it should be fine :-)

More Linux users welcome for testing on different distros, please call for action on our dev@ mailing list :-)

Barto22 · 2026-01-14T04:41:40Z

Thank you @Barto22 :-) You may want to replicate our CI build process for Linux too that could be best benchmark for comparison :-)

If that works fine locally and here on github then it should be fine :-)

More Linux users welcome for testing on different distros, please call for action on our dev@ mailing list :-)

Of course. I'm testing all CI builds and I will fix the errors,if anyone want to join testing I can share the docker already builded image.

Barto22 · 2026-01-14T04:44:00Z

Question for @Barto22 and everyone:

Does this bump resolve the known issues?

#16896

Before proceeding with the merge, I would recommend testing the new Nuttx Docker image by compiling all <board name>:<board configuration>.

We also need to check the toolchain update for the other operating systems (macOS and Windows - MSYS2/Native) present in the CI, so that the update does not leave anyone behind.

Otherwise, there is a risk that all attention will be focused on one OS at the expense of others.

For example macOS issues on NuttX Mirror

#17818

I remind myself and everyone else:

The Inviolable Principles of NuttX

https://nuttx.apache.org/docs/latest/introduction/inviolables.html#all-users-matter

I will update all CI scripts according to results from tests of Docker image. But I will really appreciate tests on other platforms cause I'm mainly working on Linux.

All tools are updated to most recent stable versions. Signed-off-by: Bartosz <bartol2205@gmail.com>

Barto22 · 2026-01-14T13:57:57Z

I have updated in Dockerfile all tools to most recent versions, compilers too, Ubuntu to 24.04 LTS from 22.04. GCC and G++ are in version 15.2 so after merging my PR #17826 there will be no need of using clang for SIM boards tests - but clang is also in latest stable version 21, so I will remove this PR: #17850 because there will be no need of using clang for SIM board tests with libcxx. Now I'm working on fixing the compile errors and I will get back with the results.

Change GCC versions to older ones. Signed-off-by: Bartosz <bartol2205@gmail.com>

/nuttx/drivers/video/: Fix uninitialized variables Fix compile errors. Signed-off-by: Bartosz <bartol2205@gmail.com>

Barto22 · 2026-01-16T12:26:38Z

For now Ubuntu 24.04 does not provide a package for GCC 15. Because of that, in this PR I will only update GCC (and the related toolchains) to version 14. The upcoming Ubuntu 26 LTS release on April is expected to include GCC 15 packages, so once that is available I plan to update the Dockerfile again to move the toolchains to the latest versions.

Regarding Clang/LLVM: the embedded LLVM/Clang toolchain currently has stable builds only up to version 19. Because of this, in my other PR (#17826) I will revert the libc++ and libc++abi versions to the latest stable v19 release - which will be still newer that current version v17. Version 21 (as used now) is not supported by the ARM embedded toolchain v19, so upgrading to it causes unnecessary problems for other users.

The intent of these changes is to update NuttX’s Docker environment to modern stable toolchain versions (even if not the very latest) so that we can benefit from the recent improvements while avoiding known breakage. After the Ubuntu release lands we can then move forward to GCC 15 and embedded Clang/LLVM 20 which is pre-relase for now (https://github.com/ARM-software/LLVM-embedded-toolchain-for-Arm/releases), which should also allow us to move libc++/libc++abi forward again.

I’ll run all the builds over the weekend and push fixes for any issues introduced by the current Dockerfile changes with new upragded toolchains. I think it's worth to even update this tools now because newer compilers will have a chance to catch more bugs, as it does now.

cederom · 2026-01-19T12:10:59Z

Thank you @Barto22 :-) Yes, small reasonable steps, measurable results :-)

We are quite conservative here, not necessarily follow bleeding edge fashions, quite the opposite we prefer "unix old-school" and what works best. For instance we prefer stable 14.2 gcc as most users use it and work with C. There are not that many C++ users here so updating compilers / libstdc++ should be well justified and must not break anything for anyone else. No problem to wait for new LTS release of build host OS. There is no need to switch at the day of release unless we are sure all works as expected and there are no known growing pains. We prefer long-term self-compatibility over short-lived modernity :-)

As you can see we have many limitations, including the GH Runners quotas, that were strongly exceeded by just few GCC 15 builds plus end of year in CN that usually results in increased CI usage.

cederom · 2026-01-19T12:13:43Z

arch/arm/src/nrf52/nrf52_tickless_rtc.c


  leave_critical_section(flags);
-
-  return OK;


Why code changes when PR is about Docker configuration update? This is out of scope and hidden change that impacts existing code. If this fixes some other issue this should be provided as separate PR.

Please give a careful read to: https://github.com/apache/nuttx/blob/master/CONTRIBUTING.md

cederom · 2026-01-19T12:17:05Z