Comment 2 for bug 1941899

I analyzed this issue in depth and discovered that the root cause of arm-none-eabi-gcc.exe being linked dynamically against libgcc_s_sjlj-1.dll and libstdc++6.dll was not related to GCC configure flags like "--disable-sjlj-exceptions". In my local build (driven by build-toolchain.sh), "make all-gcc" was followed by "make install-gcc" - the install target triggered rebuild of all toolchain binaries due to incorrect timestamp of one of the prerequisite libraries (the issue is visible in the build log as make warning "file has modification time in the future"). The binaries produced by "make all-gcc" were linked statically against the mingw runtime libraries, while the binaries produced by "make install-gcc" - linked dynamically for unidentified reason. Once I fixed my build scripts to avoid the make timestamp issue, "install-gcc" no longer replaced static binaries with dynamic binaries, and the resulting toolchain was correct.

Please close this ticket as there is no issue in GCC configure scripts and build scripts in Arm source package.