The following is extracted from a post by Ray Donnelly, a MinGW-w64 contributor. It enlightens on the subject and is essential preamble to my question. There are 3 systems, MSYS2 and 32-bit and 64-bit Native Windows systems. Each system has its own repository of software packages in the MSYS2 distribution. […] that is an important … Read more
This is a result of a non-standard declaration of vswprintf on Windows. The GNU Standard Library defines _GLIBCXX_HAVE_BROKEN_VSWPRINTF on this platform, which in turn disables the conversion functions you’re attempting to use. You can read more about this issue and macro here: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37522. If you’re willing to modify the header files distributed with MinGW, you … Read more
It’s not an exception. It’s an error which is determined at hardware level and is returned back to the operating system, which then notifies your program in some OS-specific way about it (like, by killing the process). I believe that in such case what happens is not an exception but a signal. If it’s the … Read more
Answering myself but I managed to find the perfect library for OLE/COM calling in non-Microsoft compilers : disphelper. (it’s available from sourceforge.net under a permissive BSD license). It works both in C and C++ (and thus any other language with C bindings as well). It uses a printf/scanf-like format string syntax. (You pass whatever you … Read more
The first step is to compile your program with -g to include debugging information within the executable: g++ -g -o myprog.exe mycode.cpp Then the program can be loaded into gdb: gdb myprog.exe A few commands to get you started: break main will cause the debugger to break when main is called. You can also break … Read more
I suspect GCC (mingw) has custom code to disable the checks for the wide printf functions on Windows. This is because Microsoft’s own implementation (MSVCRT) is badly wrong and has %s and %ls backwards for the wide printf functions; since GCC can’t be sure whether you will be linking with MS’s broken implementation or some … Read more
Although an old question, none of the answers here helped me. The only route I found to get to my destination is by typing in the following line in my command prompt: To copy: set Path=C:\MinGW\bin;%PATH% After that, simply type in gcc -v. Hope this helps anyone with the problem I had!
This is an extract from a personal how-to I wrote. It has since been transformed to a script (look at the OpenSSL section, obviously). It assumes you have a working installation of MinGW and that you have a working MSys console. OpenSSL To build OpenSSL, you need a working Perl installation. Download OpenSSL from its … Read more
That depends on which variant of toolchain you’re currently using. Both DWARF and SEH variants (which come starting from GCC 4.8.0) are only single-target. You can see it yourself by inspecting the directory structure of their distributions, i.e. they contain only the libraries with either 64- or 32-bit addressing, but not both. On the other … Read more
One option, though dangerous, is to convince GCC to omit the ABI-required leading underscore. -fleading-underscore This option and its counterpart, -fno-leading-underscore, forcibly change the way C symbols are represented in the object file. One use is to help link with legacy assembly code. Warning: the -fleading-underscore switch causes GCC to generate code that is not … Read more