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.

cederom · 2026-01-14T14:52:05Z

Hmm I am working on BSD, macOS also uses Clang. Do you mean you want to replace Clang with GCC 15.2 everywhere? There are some differences and some people prefer Clang. It would be nice to keep Clang build coverage.

Also as @raiden00pl pointed out in #17850 it is possible to pass build time parameter which toolchain to use.

Maybe SIM build with Clang AND Gcc is possible / desired?

Barto22 · 2026-01-14T15:04:28Z

Hmm I am working on BSD, macOS also uses Clang. Do you mean you want to replace Clang with GCC 15.2 everywhere? There are some differences and some people prefer Clang. It would be nice to keep Clang build coverage.

Also as @raiden00pl pointed out in #17850 it is possible to pass build time parameter which toolchain to use.

Maybe SIM build with Clang AND Gcc is possible / desired?

I mean I will not touch current test builds configurations. Of course Clang will stay, I updated it to version 21 cause I also use it mostly as GCC alternative and for build comparison and checks.

simbit18 · 2026-01-14T15:16:15Z

@Barto22 Why is it necessary to completely update the Dockerfile?

Wouldn't it be preferable to update it step by step?

I quickly tested only job arm-01 and found these errors.

====================================================================================
Configuration/Tool: spresense/camera,CONFIG_ARM_TOOLCHAIN_GNU_EABI
2026-01-14 11:17:43
------------------------------------------------------------------------------------
  Cleaning...
  Configuring...
  Disabling CONFIG_ARM_TOOLCHAIN_GNU_EABI
  Enabling CONFIG_ARM_TOOLCHAIN_GNU_EABI
  Building NuttX...
In file included from /__w/nuttx-bump/nuttx-bump/nuttxspace/nuttx/include/nuttx/video/v4l2_cap.h:29,
                 from video/v4l2_cap.c:35:
video/v4l2_cap.c: In function 'start_capture':
video/v4l2_cap.c:802:3: error: pointer/integer type mismatch in conditional expression [-Wint-conversion]
  802 |   IMGDATA_SET_BUF(cmng->imgdata,
      |   ^~~~~~~~~~~~~~~
video/v4l2_cap.c: In function 'complete_capture':
video/v4l2_cap.c:2035:11: error: pointer/integer type mismatch in conditional expression [-Wint-conversion]
 2035 |           IMGDATA_SET_BUF(cmng->imgdata,
      |           ^~~~~~~~~~~~~~~
make[1]: *** [Makefile:109: v4l2_cap.o] Error 1
video/isx019.c: In function 'set_spot_position':
video/isx019.c:2621:6: error: 'w' may be used uninitialized [-Werror=maybe-uninitialized]
 2621 |   if ((x >= w) || (y >= h))
      |      ^
video/isx019.c:2599:12: note: 'w' was declared here
 2599 |   uint16_t w;
      |            ^
video/isx019.c:2621:16: error: 'h' may be used uninitialized [-Werror=maybe-uninitialized]
 2621 |   if ((x >= w) || (y >= h))
      |       ~~~~~~~~~^~~~~~~~~~~
video/isx019.c:2600:12: note: 'h' was declared here
 2600 |   uint16_t h;
      |            ^
In function 'restore_spot_position',
    inlined from 'get_spot_position' at video/isx019.c:3343:7:
video/isx019.c:3293:13: error: 'w' may be used uninitialized [-Werror=maybe-uninitialized]
 3293 |   ret = ret * sz / basis;
      |         ~~~~^~~~
video/isx019.c: In function 'get_spot_position':
video/isx019.c:3325:12: note: 'w' was declared here
 3325 |   uint16_t w;
      |            ^
In function 'restore_spot_position',
    inlined from 'get_spot_position' at video/isx019.c:3345:7:
video/isx019.c:3293:13: error: 'h' may be used uninitialized [-Werror=maybe-uninitialized]
 3293 |   ret = ret * sz / basis;
      |         ~~~~^~~~
video/isx019.c: In function 'get_spot_position':
video/isx019.c:3326:12: note: 'h' was declared here
 3326 |   uint16_t h;
      |            ^
cc1: all warnings being treated as errors
make[1]: *** [Makefile:109: isx019.o] Error 1
make[1]: Target 'libdrivers.a' not remade because of errors.
make: *** [tools/LibTargets.mk:107: drivers/libdrivers.a] Error 2
make: Target 'all' not remade because of errors.
/__w/nuttx-bump/nuttx-bump/nuttxspace/nuttx/tools/testbuild.sh: line 385: /__w/nuttx-bump/nuttx-bump/nuttxspace/nuttx/../nuttx/nuttx.manifest: No such file or directory
  [1/1] Normalize spresense/camera

====================================================================================
Configuration/Tool: spresense/example_camera,CONFIG_ARM_TOOLCHAIN_GNU_EABI
2026-01-14 11:21:53
------------------------------------------------------------------------------------
  Cleaning...
  Configuring...
  Disabling CONFIG_ARM_TOOLCHAIN_GNU_EABI
  Enabling CONFIG_ARM_TOOLCHAIN_GNU_EABI
  Building NuttX...
In file included from /__w/nuttx-bump/nuttx-bump/nuttxspace/nuttx/include/nuttx/video/v4l2_cap.h:29,
                 from video/v4l2_cap.c:35:
video/v4l2_cap.c: In function 'start_capture':
video/v4l2_cap.c:802:3: error: pointer/integer type mismatch in conditional expression [-Wint-conversion]
  802 |   IMGDATA_SET_BUF(cmng->imgdata,
      |   ^~~~~~~~~~~~~~~
video/v4l2_cap.c: In function 'complete_capture':
video/v4l2_cap.c:2035:11: error: pointer/integer type mismatch in conditional expression [-Wint-conversion]
 2035 |           IMGDATA_SET_BUF(cmng->imgdata,
      |           ^~~~~~~~~~~~~~~
make[1]: *** [Makefile:109: v4l2_cap.o] Error 1
video/isx019.c: In function 'set_spot_position':
video/isx019.c:2621:6: error: 'w' may be used uninitialized [-Werror=maybe-uninitialized]
 2621 |   if ((x >= w) || (y >= h))
      |      ^
video/isx019.c:2599:12: note: 'w' was declared here
 2599 |   uint16_t w;
      |            ^
video/isx019.c:2621:16: error: 'h' may be used uninitialized [-Werror=maybe-uninitialized]
 2621 |   if ((x >= w) || (y >= h))
      |       ~~~~~~~~~^~~~~~~~~~~
video/isx019.c:2600:12: note: 'h' was declared here
 2600 |   uint16_t h;
      |            ^
In function 'restore_spot_position',
    inlined from 'get_spot_position' at video/isx019.c:3343:7:
video/isx019.c:3293:13: error: 'w' may be used uninitialized [-Werror=maybe-uninitialized]
 3293 |   ret = ret * sz / basis;
      |         ~~~~^~~~
video/isx019.c: In function 'get_spot_position':
video/isx019.c:3325:12: note: 'w' was declared here
 3325 |   uint16_t w;
      |            ^
In function 'restore_spot_position',
    inlined from 'get_spot_position' at video/isx019.c:3345:7:
video/isx019.c:3293:13: error: 'h' may be used uninitialized [-Werror=maybe-uninitialized]
 3293 |   ret = ret * sz / basis;
      |         ~~~~^~~~
video/isx019.c: In function 'get_spot_position':
video/isx019.c:3326:12: note: 'h' was declared here
 3326 |   uint16_t h;
      |            ^
cc1: all warnings being treated as errors
make[1]: *** [Makefile:109: isx019.o] Error 1
make[1]: Target 'libdrivers.a' not remade because of errors.
make: *** [tools/LibTargets.mk:107: drivers/libdrivers.a] Error 2
make: Target 'all' not remade because of errors.
/__w/nuttx-bump/nuttx-bump/nuttxspace/nuttx/tools/testbuild.sh: line 385: /__w/nuttx-bump/nuttx-bump/nuttxspace/nuttx/../nuttx/nuttx.manifest: No such file or directory
  [1/1] Normalize spresense/example_camera
====================================================================================
Configuration/Tool: spresense/mpy,CONFIG_ARM_TOOLCHAIN_GNU_EABI
2026-01-14 11:22:37
------------------------------------------------------------------------------------
  Cleaning...
  Configuring...
  Disabling CONFIG_ARM_TOOLCHAIN_GNU_EABI
  Enabling CONFIG_ARM_TOOLCHAIN_GNU_EABI
  Building NuttX...
In file included from /__w/nuttx-bump/nuttx-bump/nuttxspace/nuttx/include/nuttx/video/v4l2_cap.h:29,
                 from video/v4l2_cap.c:35:
video/v4l2_cap.c: In function 'start_capture':
video/v4l2_cap.c:802:3: error: pointer/integer type mismatch in conditional expression [-Wint-conversion]
  802 |   IMGDATA_SET_BUF(cmng->imgdata,
      |   ^~~~~~~~~~~~~~~
video/v4l2_cap.c: In function 'complete_capture':
video/v4l2_cap.c:2035:11: error: pointer/integer type mismatch in conditional expression [-Wint-conversion]
 2035 |           IMGDATA_SET_BUF(cmng->imgdata,
      |           ^~~~~~~~~~~~~~~
make[1]: *** [Makefile:109: v4l2_cap.o] Error 1
make[1]: Target 'libdrivers.a' not remade because of errors.
make: *** [tools/LibTargets.mk:107: drivers/libdrivers.a] Error 2
make: Target 'all' not remade because of errors.
/__w/nuttx-bump/nuttx-bump/nuttxspace/nuttx/tools/testbuild.sh: line 385: /__w/nuttx-bump/nuttx-bump/nuttxspace/nuttx/../nuttx/nuttx.manifest: No such file or directory
  [1/1] Normalize spresense/mpy
====================================================================================

cederom · 2026-01-14T15:25:51Z

tools/ci/docker/linux/Dockerfile

-# Configure out base setup for adding python packages
+# Download, build and install GCC 15.2.0
+RUN mkdir -p /tmp/gcc-build && cd /tmp/gcc-build && \
+  wget -q https://ftp.gnu.org/gnu/gcc/gcc-15.2.0/gcc-15.2.0.tar.xz && \


Ugh, do we really need to compile the compiler on each CI run? This will starve us from service quotas really quickly.. which we already hit several times.

If we can use no LTS version of Ubuntu we can download as package GCC version 15.

cederom · 2026-01-14T15:30:48Z

Do I get this right that you want to build the whole GCC 15.2 from sources @Barto22? Is GCC package unavailable?

This is a lot more work than building the NuttX itself and seems out of scope. This will drain us from CI quotas rapidly after several forced pushes. We already limited CI due to hitting build quotas several times. Also for this reason macOS is disabled :-(

Would it be possible to provide time / cpu usage comparison between current CI setup and your proposition?

If we are supposed to build GCC 15.2 on our own on each CI run this seems a blocker here. But it may be solved by providing system package to the build host so we could just fetch a binary package :-)

Barto22 · 2026-01-14T15:37:35Z

Do I get this right that you want to build the whole GCC 15.2 from sources @Barto22? Is GCC package unavailable?

This is a lot more work than building the NuttX itself and seems out of scope. This will drain us from CI quotas rapidly after several forced pushes. We already limited CI due to hitting build quotas several times. Also for this reason macOS is disabled :-(

Would it be possible to provide time / cpu usage comparison between current CI setup and your proposition?

If we are supposed to build GCC 15.2 on our own on each CI run this seems a blocker here. But it may be solved by providing system package to the build host so we could just fetch a binary package :-)

The GCC 15 is available from Ubuntu 25 so if we can use no LTS version of Ubuntu it will be possible to pull GCC 15 as package, I will check that.

Barto22 · 2026-01-14T15:39:53Z

@Barto22 Why is it necessary to completely update the Dockerfile?

Wouldn't it be preferable to update it step by step?

I quickly tested only job arm-01 and found these errors.


====================================================================================

Configuration/Tool: spresense/camera,CONFIG_ARM_TOOLCHAIN_GNU_EABI

2026-01-14 11:17:43

------------------------------------------------------------------------------------

  Cleaning...

  Configuring...

  Disabling CONFIG_ARM_TOOLCHAIN_GNU_EABI

  Enabling CONFIG_ARM_TOOLCHAIN_GNU_EABI

  Building NuttX...

In file included from /__w/nuttx-bump/nuttx-bump/nuttxspace/nuttx/include/nuttx/video/v4l2_cap.h:29,

                 from video/v4l2_cap.c:35:

video/v4l2_cap.c: In function 'start_capture':

video/v4l2_cap.c:802:3: error: pointer/integer type mismatch in conditional expression [-Wint-conversion]

  802 |   IMGDATA_SET_BUF(cmng->imgdata,

      |   ^~~~~~~~~~~~~~~

video/v4l2_cap.c: In function 'complete_capture':

video/v4l2_cap.c:2035:11: error: pointer/integer type mismatch in conditional expression [-Wint-conversion]

 2035 |           IMGDATA_SET_BUF(cmng->imgdata,

      |           ^~~~~~~~~~~~~~~

make[1]: *** [Makefile:109: v4l2_cap.o] Error 1

video/isx019.c: In function 'set_spot_position':

video/isx019.c:2621:6: error: 'w' may be used uninitialized [-Werror=maybe-uninitialized]

 2621 |   if ((x >= w) || (y >= h))

      |      ^

video/isx019.c:2599:12: note: 'w' was declared here

 2599 |   uint16_t w;

      |            ^

video/isx019.c:2621:16: error: 'h' may be used uninitialized [-Werror=maybe-uninitialized]

 2621 |   if ((x >= w) || (y >= h))

      |       ~~~~~~~~~^~~~~~~~~~~

video/isx019.c:2600:12: note: 'h' was declared here

 2600 |   uint16_t h;

      |            ^

In function 'restore_spot_position',

    inlined from 'get_spot_position' at video/isx019.c:3343:7:

video/isx019.c:3293:13: error: 'w' may be used uninitialized [-Werror=maybe-uninitialized]

 3293 |   ret = ret * sz / basis;

      |         ~~~~^~~~

video/isx019.c: In function 'get_spot_position':

video/isx019.c:3325:12: note: 'w' was declared here

 3325 |   uint16_t w;

      |            ^

In function 'restore_spot_position',

    inlined from 'get_spot_position' at video/isx019.c:3345:7:

video/isx019.c:3293:13: error: 'h' may be used uninitialized [-Werror=maybe-uninitialized]

 3293 |   ret = ret * sz / basis;

      |         ~~~~^~~~

video/isx019.c: In function 'get_spot_position':

video/isx019.c:3326:12: note: 'h' was declared here

 3326 |   uint16_t h;

      |            ^

cc1: all warnings being treated as errors

make[1]: *** [Makefile:109: isx019.o] Error 1

make[1]: Target 'libdrivers.a' not remade because of errors.

make: *** [tools/LibTargets.mk:107: drivers/libdrivers.a] Error 2

make: Target 'all' not remade because of errors.

/__w/nuttx-bump/nuttx-bump/nuttxspace/nuttx/tools/testbuild.sh: line 385: /__w/nuttx-bump/nuttx-bump/nuttxspace/nuttx/../nuttx/nuttx.manifest: No such file or directory

  [1/1] Normalize spresense/camera



====================================================================================

Configuration/Tool: spresense/example_camera,CONFIG_ARM_TOOLCHAIN_GNU_EABI

2026-01-14 11:21:53

------------------------------------------------------------------------------------

  Cleaning...

  Configuring...

  Disabling CONFIG_ARM_TOOLCHAIN_GNU_EABI

  Enabling CONFIG_ARM_TOOLCHAIN_GNU_EABI

  Building NuttX...

In file included from /__w/nuttx-bump/nuttx-bump/nuttxspace/nuttx/include/nuttx/video/v4l2_cap.h:29,

                 from video/v4l2_cap.c:35:

video/v4l2_cap.c: In function 'start_capture':

video/v4l2_cap.c:802:3: error: pointer/integer type mismatch in conditional expression [-Wint-conversion]

  802 |   IMGDATA_SET_BUF(cmng->imgdata,

      |   ^~~~~~~~~~~~~~~

video/v4l2_cap.c: In function 'complete_capture':

video/v4l2_cap.c:2035:11: error: pointer/integer type mismatch in conditional expression [-Wint-conversion]

 2035 |           IMGDATA_SET_BUF(cmng->imgdata,

      |           ^~~~~~~~~~~~~~~

make[1]: *** [Makefile:109: v4l2_cap.o] Error 1

video/isx019.c: In function 'set_spot_position':

video/isx019.c:2621:6: error: 'w' may be used uninitialized [-Werror=maybe-uninitialized]

 2621 |   if ((x >= w) || (y >= h))

      |      ^

video/isx019.c:2599:12: note: 'w' was declared here

 2599 |   uint16_t w;

      |            ^

video/isx019.c:2621:16: error: 'h' may be used uninitialized [-Werror=maybe-uninitialized]

 2621 |   if ((x >= w) || (y >= h))

      |       ~~~~~~~~~^~~~~~~~~~~

video/isx019.c:2600:12: note: 'h' was declared here

 2600 |   uint16_t h;

      |            ^

In function 'restore_spot_position',

    inlined from 'get_spot_position' at video/isx019.c:3343:7:

video/isx019.c:3293:13: error: 'w' may be used uninitialized [-Werror=maybe-uninitialized]

 3293 |   ret = ret * sz / basis;

      |         ~~~~^~~~

video/isx019.c: In function 'get_spot_position':

video/isx019.c:3325:12: note: 'w' was declared here

 3325 |   uint16_t w;

      |            ^

In function 'restore_spot_position',

    inlined from 'get_spot_position' at video/isx019.c:3345:7:

video/isx019.c:3293:13: error: 'h' may be used uninitialized [-Werror=maybe-uninitialized]

 3293 |   ret = ret * sz / basis;

      |         ~~~~^~~~

video/isx019.c: In function 'get_spot_position':

video/isx019.c:3326:12: note: 'h' was declared here

 3326 |   uint16_t h;

      |            ^

cc1: all warnings being treated as errors

make[1]: *** [Makefile:109: isx019.o] Error 1

make[1]: Target 'libdrivers.a' not remade because of errors.

make: *** [tools/LibTargets.mk:107: drivers/libdrivers.a] Error 2

make: Target 'all' not remade because of errors.

/__w/nuttx-bump/nuttx-bump/nuttxspace/nuttx/tools/testbuild.sh: line 385: /__w/nuttx-bump/nuttx-bump/nuttxspace/nuttx/../nuttx/nuttx.manifest: No such file or directory

  [1/1] Normalize spresense/example_camera

====================================================================================

Configuration/Tool: spresense/mpy,CONFIG_ARM_TOOLCHAIN_GNU_EABI

2026-01-14 11:22:37

------------------------------------------------------------------------------------

  Cleaning...

  Configuring...

  Disabling CONFIG_ARM_TOOLCHAIN_GNU_EABI

  Enabling CONFIG_ARM_TOOLCHAIN_GNU_EABI

  Building NuttX...

In file included from /__w/nuttx-bump/nuttx-bump/nuttxspace/nuttx/include/nuttx/video/v4l2_cap.h:29,

                 from video/v4l2_cap.c:35:

video/v4l2_cap.c: In function 'start_capture':

video/v4l2_cap.c:802:3: error: pointer/integer type mismatch in conditional expression [-Wint-conversion]

  802 |   IMGDATA_SET_BUF(cmng->imgdata,

      |   ^~~~~~~~~~~~~~~

video/v4l2_cap.c: In function 'complete_capture':

video/v4l2_cap.c:2035:11: error: pointer/integer type mismatch in conditional expression [-Wint-conversion]

 2035 |           IMGDATA_SET_BUF(cmng->imgdata,

      |           ^~~~~~~~~~~~~~~

make[1]: *** [Makefile:109: v4l2_cap.o] Error 1

make[1]: Target 'libdrivers.a' not remade because of errors.

make: *** [tools/LibTargets.mk:107: drivers/libdrivers.a] Error 2

make: Target 'all' not remade because of errors.

/__w/nuttx-bump/nuttx-bump/nuttxspace/nuttx/tools/testbuild.sh: line 385: /__w/nuttx-bump/nuttx-bump/nuttxspace/nuttx/../nuttx/nuttx.manifest: No such file or directory

  [1/1] Normalize spresense/mpy

====================================================================================

I will check that errors, I see that this are mostly some int conversion errors, I will check that. Thanks for pointing out.

cederom · 2026-01-14T19:52:16Z

@Barto22: The GCC 15 is available from Ubuntu 25 so if we can use no LTS version of Ubuntu it will be possible to pull GCC 15 as package, I will check that.

We prefer LTS. Too many changes in non-lts. And its good common reference point.

Please contact Ubuntu package managers and ask for GCC 15.2 package. Without this package ready for use this change will be hard to merge as it puts too much burden on the compiler build rather than NuttX builds. If you need support / confirmation form our side let us know :-)

cederom

Building GCC 15.2 from source on each CI invocation will exhaust our CI quota rapidly. This is far more work than NuttX build itself.
We want to stick to LTS releases for the build machines.
Please request for GCC 15.2 package for the build host.

Barto22 · 2026-01-14T20:03:09Z

Ok, I will let know about update for GCC 15 on Ubuntu.

cederom · 2026-01-15T15:27:00Z

Look here #17914 @Barto22 we already run out of runners with "standard" daily PR reviews. There is absolutely no way we can build GCC on each run, we need to use the package, preferably something already offered by GitHub or Ubuntu just to make runner time as short as possible (but not shorter :-) ).

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.

tools/ci/docker/: Update toolchains and clang to latest version

f8795d0

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

Barto22 requested review from btashton, simbit18 and xiaoxiang781216 as code owners January 13, 2026 06:45

github-actions bot added Area: Tooling Area: CI Size: S The size of the change in this PR is small labels Jan 13, 2026

xiaoxiang781216 previously approved these changes Jan 13, 2026

View reviewed changes

This was referenced Jan 13, 2026

libs: Add support for latest LLVM LIBCXX and LIBCXXABI version 21.1.8 #17826

Open

Change SIM boards that uses libcxx to use Clang. #17850

Closed

simbit18 requested review from acassis, cederom, hartmannathan, jerpelea, linguini1, lupyuen and raiden00pl January 13, 2026 11:39

lupyuen approved these changes Jan 13, 2026

View reviewed changes

lupyuen requested changes Jan 13, 2026

View reviewed changes

/tools/docker/: Update all tools to most recent version

c419476

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

Barto22 dismissed xiaoxiang781216’s stale review via c419476 January 14, 2026 13:54

github-actions bot added the Size: M The size of the change in this PR is medium label Jan 14, 2026

cederom reviewed Jan 14, 2026

View reviewed changes

cederom requested changes Jan 14, 2026

View reviewed changes

cederom marked this pull request as draft January 15, 2026 22:09

cederom mentioned this pull request Jan 15, 2026

[Warning] High Utilisation of GitHub Runners #17914

Open

1 task

Barto22 added 2 commits January 16, 2026 07:25

/tools/docker/: Change GCC to version from PPA 14.3 and other tools also

553f44e

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

/nuttx/include/: Fix macro

fe91b9e

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

github-actions bot added the Area: Video label Jan 16, 2026

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

Are you sure you want to change the base?

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

Conversation

Barto22 commented Jan 13, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Impact

Testing

Uh oh!

simbit18 commented Jan 13, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

lupyuen left a comment

Choose a reason for hiding this comment

Uh oh!

lupyuen commented Jan 13, 2026

Uh oh!

Barto22 commented Jan 13, 2026

Uh oh!

Barto22 commented Jan 13, 2026

Uh oh!

cederom commented Jan 13, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Barto22 commented Jan 14, 2026

Uh oh!

Barto22 commented Jan 14, 2026

Uh oh!

Barto22 commented Jan 14, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

cederom commented Jan 14, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Barto22 commented Jan 14, 2026

Uh oh!

simbit18 commented Jan 14, 2026

Uh oh!

cederom Jan 14, 2026

Choose a reason for hiding this comment

Uh oh!

Barto22 Jan 14, 2026

Choose a reason for hiding this comment

Uh oh!

cederom commented Jan 14, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Barto22 commented Jan 14, 2026

Uh oh!

Barto22 commented Jan 14, 2026

Uh oh!

cederom commented Jan 14, 2026

Uh oh!

cederom left a comment

Choose a reason for hiding this comment

Uh oh!

Barto22 commented Jan 14, 2026

Uh oh!

cederom commented Jan 15, 2026

Uh oh!

Barto22 commented Jan 16, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

Barto22 commented Jan 13, 2026 •

edited

Loading

simbit18 commented Jan 13, 2026 •

edited

Loading

cederom commented Jan 13, 2026 •

edited

Loading

Barto22 commented Jan 14, 2026 •

edited

Loading

cederom commented Jan 14, 2026 •

edited

Loading

cederom commented Jan 14, 2026 •

edited

Loading