I'd like to suggest the following Q&A for the FAQ:
--//--
Q: Why do some 32-bit MinGW-w64 applications fail with '... _vswprintf
could not be located in the dynamic link library msvcrt.dll' on Windows
XP SP1?
A: For C++, MinGW-w64 implements 'vswprintf (wchar_t *__stream, const
wchar_t *__for
On 2012-12-27 8:18 PM, John E. / TDM wrote:
>...
> In the vein of static linkage, however, I do have one observation and a
> related question. The pthreads-w32 library has startup code that is
> executed when the DLL is attached, and therefore when the library is
> statically linked, the user must
e to the end user).
(2) Depending on how one interprets "via the same media that the binary
was delivered", I'm not sure that all of the major distros would achieve
that. If for example I obtain a libstdc++.so via an
64-mingw32-c++.exe in
"i686-w64-mingw32-gcc-4.7.1-2-release-win64_rubenvb\mingw32\bin" does work.
Regards,
Herb Thompson
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today
ld.exe:
skipping incompatible
c:/opt/mingw32-gcc-4.7.0-2_rubenvb/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.7.0/../../../libstdc++.dll.a
when searching for -lstdc++
Is -m32 not valid with the 64-bit tools?
Regards,
Herb Thompson
-