The GCC build does not work with MingW/TDM about cmdcolor

[BobVul]

This is actually fixed in TDM-GCC 4.8.1:

The "-static-libstdc++" option, though still unnecessary, no longer causes a compilation error.

[alecmev]

As far as I know, GCC uses the shared version of libstdc++, if it's available:

When the g++ program is used to link a C++ program, it normally automatically links against libstdc++. If libstdc++ is available as a shared library, and the -static option is not used, then this links against the shared version of libstdc++. Source.

That's why I've specified it explicitly. However, I could probably just reduce it to -static.

[BobVul]

TDM-GCC is, ah... different from vanilla GCC. From their quirks page:

• TDM-GCC doesn't link your programs with the libgcc or libstdc++ runtime DLLs by default.
• Other toolchains default to DLL runtime linkage in order to allow you to throw exceptions among DLLs and EXEs.
• TDM-GCC lets you throw exceptions among DLLs and EXEs even with the static runtime.
• Your programs will not rely on any additional DLLs when compiling with default options.
• TDM-GCC still includes DLL versions of the libgcc and libstdc++ runtimes, which you can enable for your program with "-shared-libgcc" and "-shared-libstdc++" if desired.

As quoted earlier, the -static-libstdc++ option was only added in 4.8.1.

TDM-GCC is fairly popular as a Win32 port of GCC (the other major one being MingW, which TDM-GCC is based on). It's also the default for Code::Blocks. So, not exactly obscure, but considering they've fixed it in the latest version it matters even less now.

[alecmev]

I see. But still, replacing -static-libgcc -static-libstdc++ with -static probably wouldn't hurt anybody, while adding out-of-the-box compatibility with older versions of TDM-GCC.