The link commandline argument -static-libgcc should work. Another variant you could try is plain -static. If you don’t want to worry about this, and still want to redistribute your binary, just copy the relevant dll from MinGW’s bin directory and place it alongside your executable. This is common practice and works as advertised.
glibc uses libnss to support a number of different providers for address resolution services. Unfortunately, you cannot statically link libnss, as exactly what providers it loads depends on the local system’s configuration.
The reasons given in other answers are correct, but they are not the most important reason. The most important reason why glibc should not be statically linked, is that it makes extensive internal use of dlopen, to load NSS (Name Service Switch) modules and iconv conversions. The modules themselves refer to C library functions. If … Read more
If your toolchain includes the static winpthreads, adding the option -static Will pull in static versions of all libraries it can. Alternatively, you can remove libwinpthread.dll.a and the DLL itself from the toolchain directories. This might mess up programs linking with libstdc++ and libgcc DLLs though, so be careful. A third option is to use … Read more
Concepts Minimum concept of what such a shared library maybe about. same code different data There are variations on this. Do you support linking between libraries. Are the references a DAG structure or fully cyclic? Do you want to put the code in ROM, or support code updates? Do you wish to load libraries after … Read more
GNU libc is not designed to be statically linked. Important functions, e.g. gethostbyname and iconv, will malfunction or not work at all in a static binary. Arguably even worse, under some conditions a static binary will attempt to dynamically open and use libc.so.6, even though the whole point of static linkage is to avoid such … Read more
Before iOS8, Xcode only allowed the option of creating static libraries for iOS. The common problem with that was we had to ship the binary and headers separately. Later, some developers came with the idea of creating ‘static frameworks’. [the .framework is just a folder with symbolic links to the lib and the headers]. One … Read more
I think this is very annoying, and I think it is arrogant to call a feature “useless” because it has problems dealing with certain use cases. The biggest problem with the glibc approach is that it hard-codes paths to system libraries (gconv as well as nss), and thus it breaks when people try to run … Read more
Since nobody else has come up with an answer yet, I will give it a try. Unfortunately, I don’t know that Code::Blocks IDE so my answer will only be partial. 1 How to Create a Statically Linked Executable with GCC This is not IDE specific but holds for GCC (and many other compilers) in general. … Read more