Windows 11 - Compiling toolchain (5.3 and 6)

Chris Thomas ChristopherT at
Fri Oct 13 14:32:17 UTC 2023

I would prefer to create the toolchains in an environment that is easily integrated with Windows. The method that is the least volatile is also the most attractive. I was using a laptop with Windows 11, however, it does continue to freeze during compilation in WSL2. It's running Ubuntu 22.04 LTS. This time it's been sitting at GDB for approximately 2 days. I've acquired a desktop PC and put a fresh installation of Windows 11 on it with Ubuntu 22.04 LTS in WSL2 and am going to try building RTEMS 6 toolchain on there. Hopefully it’s the difference in hardware.

Chris Thomas

-----Original Message-----
From: zhengxiaojun <17935334 at> 
Sent: Thursday, October 12, 2023 8:23 PM
To: Chris Thomas <ChristopherT at>; users at
Subject: Re: Windows 11 - Compiling toolchain (5.3 and 6)

Hello Chris,

    I used MSYS2, not all the tools can be compiled in MSYS2. MSYS2 has a pre-built dtc package, so you do not need to compile it. And ged,texinfo,gdb,rtems-tools can not build success in my MSYS2, but these tools are not essential for compiling RTEMS6. I just compile expat,gmp, binutils,gcc. I built last week, these tools should be OK.
BTW: build on windows will take a long times.

在 2023/10/12 21:59, Chris Thomas 写道:
> Good Day,
> I'm attempting to build a toolchain on Windows 11. I've followed the 
> quickstart guide for 5.3 as well as 6 and run into build errors each 
> time. I began with MSYS2 and ran into this issue:
> <>
> I implemented the work around but it throws an error with arg7nxwm1.
> Attempting to compile 6 using the quick start guide for a Windows host 
> in MSYS2's MinGW64 errors because fnmatch.h is not found. It looks 
> like its available in gnulib, which seems to be part of gdb, but this 
> error is thrown during the compilation of dtc.
> I tried moving to WSL2 and installing Ubuntu to get a true POSIX 
> environment.
> 5.3 won't compile GDB - it says "no libraries passed to compiler". So 
> I tried compiling 6 and it freezes during the gcc build.
> I've gone down a couple different avenue's trying to get a working 
> toolchain over the last few weeks. At this point, I feel as though I 
> need some advice on whether to stick with MSYS2 and try to get that 
> working or continue with WSL2. The same for the version, should I 
> continue to try to get version 6 to work? If that's the case, what is 
> my next step? There don't seem to be any packages readily available in
> MSYS2 that include fnmatch.h. And with build errors frequently 
> occurring, is there updated documentation to assist with getting started?
> Thanks,
> *Chris Thomas*
> _______________________________________________
> users mailing list
> users at

More information about the users mailing list