Re: [Mingw-w64-public] Suggestion for FAQ Re _vswprintf and msvcrt.dll on XP SP1
On 05/13/13 03:56, xunxun wrote: 于 2013/5/10 星期五 17:17, Jacek Caban 写道: On 05/10/13 11:11, xunxun wrote: 于 2013/5/9 星期四 10:40, xunxun 写道: 于 2013/5/9 星期四 6:27, Jacek Caban 写道: On 5/8/13 7:27 AM, xunxun wrote: 于 2013/1/21 星期一 21:07, Kai Tietz 写道: 2013/1/21 Jacek Caban ja...@codeweavers.com: On 01/21/13 13:39, JonY wrote: On 1/21/2013 09:43, Herb Thompson wrote: 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 *__format, __builtin_va_list __local_argv)' as a call to '_vswprintf'. Older versions of msvcrt.dll, like the version in XP SP1, do not include '_vswprintf'. A workaround for this is to compile any C++ libraries and applications that use 'vswprintf' (with the preceding signature) with -D__USE_MINGW_ANSI_STDIO. For example, to build the wxWidgets library for applications to be deployed on XP SP1, build wxWidgets with the following command line: mingw32-make -f makefile.gcc CPPFLAGS=-D__USE_MINGW_ANSI_STDIO Done as https://sourceforge.net/apps/trac/mingw-w64/wiki/_vswprintf%20missing. Thanks. I've also added a caveat section on the side effects of using __USE_MINGW_ANSI_STDIO. Well, IMO we should fix bugs instead of documenting them... I may look at this, but I'm not sure when I will find time for that. Jacek Well, in general I agree. We might should do same hack (for older msvcrt versions) as we do for vscanf (as example). Cheers, Kai Can we do _vswprintf == vswprintf again? And XP SP3 msvcrt.dll doesn't contain _vswprint, too. We must fix it! I'm sorry, I forgot about this before I found the time to fix it. Can you prepare a patch? Thanks, Jacek Same with vsnprintf Index: mingw-w64-crt/lib32/msvcrt.def.in === --- mingw-w64-crt/lib32/msvcrt.def.in(revision 5847) +++ mingw-w64-crt/lib32/msvcrt.def.in(working copy) @@ -1116,7 +1116,7 @@ _vsprintf_p _vsprintf_p_l _vsprintf_s_l -_vswprintf +_vswprintf == vswprintf _vswprintf_c _vswprintf_c_l _vswprintf_l How do you think? Can we do that workaround change before a better detect method? Yes, the patch looks good to me, thanks. But this needs Kai's approval. Thanks, Jacek Can you commit it? Sure, committed as r5856. Thanks, Jacek -- Learn Graph Databases - Download FREE O'Reilly Book Graph Databases is the definitive new guide to graph databases and their applications. This 200-page book is written by three acclaimed leaders in the field. The early access version is available now. Download your free book today! http://p.sf.net/sfu/neotech_d2d_may ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] Suggestion for FAQ Re _vswprintf and msvcrt.dll on XP SP1
于 2013/5/10 星期五 17:17, Jacek Caban 写道: On 05/10/13 11:11, xunxun wrote: 于 2013/5/9 星期四 10:40, xunxun 写道: 于 2013/5/9 星期四 6:27, Jacek Caban 写道: On 5/8/13 7:27 AM, xunxun wrote: 于 2013/1/21 星期一 21:07, Kai Tietz 写道: 2013/1/21 Jacek Caban ja...@codeweavers.com: On 01/21/13 13:39, JonY wrote: On 1/21/2013 09:43, Herb Thompson wrote: 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 *__format, __builtin_va_list __local_argv)' as a call to '_vswprintf'. Older versions of msvcrt.dll, like the version in XP SP1, do not include '_vswprintf'. A workaround for this is to compile any C++ libraries and applications that use 'vswprintf' (with the preceding signature) with -D__USE_MINGW_ANSI_STDIO. For example, to build the wxWidgets library for applications to be deployed on XP SP1, build wxWidgets with the following command line: mingw32-make -f makefile.gcc CPPFLAGS=-D__USE_MINGW_ANSI_STDIO Done as https://sourceforge.net/apps/trac/mingw-w64/wiki/_vswprintf%20missing. Thanks. I've also added a caveat section on the side effects of using __USE_MINGW_ANSI_STDIO. Well, IMO we should fix bugs instead of documenting them... I may look at this, but I'm not sure when I will find time for that. Jacek Well, in general I agree. We might should do same hack (for older msvcrt versions) as we do for vscanf (as example). Cheers, Kai Can we do _vswprintf == vswprintf again? And XP SP3 msvcrt.dll doesn't contain _vswprint, too. We must fix it! I'm sorry, I forgot about this before I found the time to fix it. Can you prepare a patch? Thanks, Jacek Same with vsnprintf Index: mingw-w64-crt/lib32/msvcrt.def.in === --- mingw-w64-crt/lib32/msvcrt.def.in(revision 5847) +++ mingw-w64-crt/lib32/msvcrt.def.in(working copy) @@ -1116,7 +1116,7 @@ _vsprintf_p _vsprintf_p_l _vsprintf_s_l -_vswprintf +_vswprintf == vswprintf _vswprintf_c _vswprintf_c_l _vswprintf_l How do you think? Can we do that workaround change before a better detect method? Yes, the patch looks good to me, thanks. But this needs Kai's approval. Thanks, Jacek Can you commit it? Thanks. -- Best Regards, xunxun -- Learn Graph Databases - Download FREE O'Reilly Book Graph Databases is the definitive new guide to graph databases and their applications. This 200-page book is written by three acclaimed leaders in the field. The early access version is available now. Download your free book today! http://p.sf.net/sfu/neotech_d2d_may ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] Suggestion for FAQ Re _vswprintf and msvcrt.dll on XP SP1
于 2013/5/9 星期四 10:40, xunxun 写道: 于 2013/5/9 星期四 6:27, Jacek Caban 写道: On 5/8/13 7:27 AM, xunxun wrote: 于 2013/1/21 星期一 21:07, Kai Tietz 写道: 2013/1/21 Jacek Caban ja...@codeweavers.com: On 01/21/13 13:39, JonY wrote: On 1/21/2013 09:43, Herb Thompson wrote: 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 *__format, __builtin_va_list __local_argv)' as a call to '_vswprintf'. Older versions of msvcrt.dll, like the version in XP SP1, do not include '_vswprintf'. A workaround for this is to compile any C++ libraries and applications that use 'vswprintf' (with the preceding signature) with -D__USE_MINGW_ANSI_STDIO. For example, to build the wxWidgets library for applications to be deployed on XP SP1, build wxWidgets with the following command line: mingw32-make -f makefile.gcc CPPFLAGS=-D__USE_MINGW_ANSI_STDIO Done as https://sourceforge.net/apps/trac/mingw-w64/wiki/_vswprintf%20missing. Thanks. I've also added a caveat section on the side effects of using __USE_MINGW_ANSI_STDIO. Well, IMO we should fix bugs instead of documenting them... I may look at this, but I'm not sure when I will find time for that. Jacek Well, in general I agree. We might should do same hack (for older msvcrt versions) as we do for vscanf (as example). Cheers, Kai Can we do _vswprintf == vswprintf again? And XP SP3 msvcrt.dll doesn't contain _vswprint, too. We must fix it! I'm sorry, I forgot about this before I found the time to fix it. Can you prepare a patch? Thanks, Jacek Same with vsnprintf Index: mingw-w64-crt/lib32/msvcrt.def.in === --- mingw-w64-crt/lib32/msvcrt.def.in(revision 5847) +++ mingw-w64-crt/lib32/msvcrt.def.in(working copy) @@ -1116,7 +1116,7 @@ _vsprintf_p _vsprintf_p_l _vsprintf_s_l -_vswprintf +_vswprintf == vswprintf _vswprintf_c _vswprintf_c_l _vswprintf_l How do you think? Can we do that workaround change before a better detect method? -- Best Regards, xunxun -- Learn Graph Databases - Download FREE O'Reilly Book Graph Databases is the definitive new guide to graph databases and their applications. This 200-page book is written by three acclaimed leaders in the field. The early access version is available now. Download your free book today! http://p.sf.net/sfu/neotech_d2d_may ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] Suggestion for FAQ Re _vswprintf and msvcrt.dll on XP SP1
On 05/10/13 11:11, xunxun wrote: 于 2013/5/9 星期四 10:40, xunxun 写道: 于 2013/5/9 星期四 6:27, Jacek Caban 写道: On 5/8/13 7:27 AM, xunxun wrote: 于 2013/1/21 星期一 21:07, Kai Tietz 写道: 2013/1/21 Jacek Caban ja...@codeweavers.com: On 01/21/13 13:39, JonY wrote: On 1/21/2013 09:43, Herb Thompson wrote: 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 *__format, __builtin_va_list __local_argv)' as a call to '_vswprintf'. Older versions of msvcrt.dll, like the version in XP SP1, do not include '_vswprintf'. A workaround for this is to compile any C++ libraries and applications that use 'vswprintf' (with the preceding signature) with -D__USE_MINGW_ANSI_STDIO. For example, to build the wxWidgets library for applications to be deployed on XP SP1, build wxWidgets with the following command line: mingw32-make -f makefile.gcc CPPFLAGS=-D__USE_MINGW_ANSI_STDIO Done as https://sourceforge.net/apps/trac/mingw-w64/wiki/_vswprintf%20missing. Thanks. I've also added a caveat section on the side effects of using __USE_MINGW_ANSI_STDIO. Well, IMO we should fix bugs instead of documenting them... I may look at this, but I'm not sure when I will find time for that. Jacek Well, in general I agree. We might should do same hack (for older msvcrt versions) as we do for vscanf (as example). Cheers, Kai Can we do _vswprintf == vswprintf again? And XP SP3 msvcrt.dll doesn't contain _vswprint, too. We must fix it! I'm sorry, I forgot about this before I found the time to fix it. Can you prepare a patch? Thanks, Jacek Same with vsnprintf Index: mingw-w64-crt/lib32/msvcrt.def.in === --- mingw-w64-crt/lib32/msvcrt.def.in(revision 5847) +++ mingw-w64-crt/lib32/msvcrt.def.in(working copy) @@ -1116,7 +1116,7 @@ _vsprintf_p _vsprintf_p_l _vsprintf_s_l -_vswprintf +_vswprintf == vswprintf _vswprintf_c _vswprintf_c_l _vswprintf_l How do you think? Can we do that workaround change before a better detect method? Yes, the patch looks good to me, thanks. But this needs Kai's approval. Thanks, Jacek -- Learn Graph Databases - Download FREE O'Reilly Book Graph Databases is the definitive new guide to graph databases and their applications. This 200-page book is written by three acclaimed leaders in the field. The early access version is available now. Download your free book today! http://p.sf.net/sfu/neotech_d2d_may ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] Suggestion for FAQ Re _vswprintf and msvcrt.dll on XP SP1
2013/5/10 Jacek Caban ja...@codeweavers.com: On 05/10/13 11:11, xunxun wrote: 于 2013/5/9 星期四 10:40, xunxun 写道: 于 2013/5/9 星期四 6:27, Jacek Caban 写道: On 5/8/13 7:27 AM, xunxun wrote: 于 2013/1/21 星期一 21:07, Kai Tietz 写道: 2013/1/21 Jacek Caban ja...@codeweavers.com: On 01/21/13 13:39, JonY wrote: On 1/21/2013 09:43, Herb Thompson wrote: 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 *__format, __builtin_va_list __local_argv)' as a call to '_vswprintf'. Older versions of msvcrt.dll, like the version in XP SP1, do not include '_vswprintf'. A workaround for this is to compile any C++ libraries and applications that use 'vswprintf' (with the preceding signature) with -D__USE_MINGW_ANSI_STDIO. For example, to build the wxWidgets library for applications to be deployed on XP SP1, build wxWidgets with the following command line: mingw32-make -f makefile.gcc CPPFLAGS=-D__USE_MINGW_ANSI_STDIO Done as https://sourceforge.net/apps/trac/mingw-w64/wiki/_vswprintf%20missing. Thanks. I've also added a caveat section on the side effects of using __USE_MINGW_ANSI_STDIO. Well, IMO we should fix bugs instead of documenting them... I may look at this, but I'm not sure when I will find time for that. Jacek Well, in general I agree. We might should do same hack (for older msvcrt versions) as we do for vscanf (as example). Cheers, Kai Can we do _vswprintf == vswprintf again? And XP SP3 msvcrt.dll doesn't contain _vswprint, too. We must fix it! I'm sorry, I forgot about this before I found the time to fix it. Can you prepare a patch? Thanks, Jacek Same with vsnprintf Index: mingw-w64-crt/lib32/msvcrt.def.in === --- mingw-w64-crt/lib32/msvcrt.def.in(revision 5847) +++ mingw-w64-crt/lib32/msvcrt.def.in(working copy) @@ -1116,7 +1116,7 @@ _vsprintf_p _vsprintf_p_l _vsprintf_s_l -_vswprintf +_vswprintf == vswprintf _vswprintf_c _vswprintf_c_l _vswprintf_l How do you think? Can we do that workaround change before a better detect method? Yes, the patch looks good to me, thanks. But this needs Kai's approval. Thanks, Jacek Yes, patch looks ok. Please apply. Thanks, Kai -- Learn Graph Databases - Download FREE O'Reilly Book Graph Databases is the definitive new guide to graph databases and their applications. This 200-page book is written by three acclaimed leaders in the field. The early access version is available now. Download your free book today! http://p.sf.net/sfu/neotech_d2d_may ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] Suggestion for FAQ Re _vswprintf and msvcrt.dll on XP SP1
On 5/8/13 7:27 AM, xunxun wrote: 于 2013/1/21 星期一 21:07, Kai Tietz 写道: 2013/1/21 Jacek Caban ja...@codeweavers.com: On 01/21/13 13:39, JonY wrote: On 1/21/2013 09:43, Herb Thompson wrote: 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 *__format, __builtin_va_list __local_argv)' as a call to '_vswprintf'. Older versions of msvcrt.dll, like the version in XP SP1, do not include '_vswprintf'. A workaround for this is to compile any C++ libraries and applications that use 'vswprintf' (with the preceding signature) with -D__USE_MINGW_ANSI_STDIO. For example, to build the wxWidgets library for applications to be deployed on XP SP1, build wxWidgets with the following command line: mingw32-make -f makefile.gcc CPPFLAGS=-D__USE_MINGW_ANSI_STDIO Done as https://sourceforge.net/apps/trac/mingw-w64/wiki/_vswprintf%20missing. Thanks. I've also added a caveat section on the side effects of using __USE_MINGW_ANSI_STDIO. Well, IMO we should fix bugs instead of documenting them... I may look at this, but I'm not sure when I will find time for that. Jacek Well, in general I agree. We might should do same hack (for older msvcrt versions) as we do for vscanf (as example). Cheers, Kai Can we do _vswprintf == vswprintf again? And XP SP3 msvcrt.dll doesn't contain _vswprint, too. We must fix it! I'm sorry, I forgot about this before I found the time to fix it. Can you prepare a patch? Thanks, Jacek -- Learn Graph Databases - Download FREE O'Reilly Book Graph Databases is the definitive new guide to graph databases and their applications. This 200-page book is written by three acclaimed leaders in the field. The early access version is available now. Download your free book today! http://p.sf.net/sfu/neotech_d2d_may ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] Suggestion for FAQ Re _vswprintf and msvcrt.dll on XP SP1
于 2013/5/9 星期四 6:27, Jacek Caban 写道: On 5/8/13 7:27 AM, xunxun wrote: 于 2013/1/21 星期一 21:07, Kai Tietz 写道: 2013/1/21 Jacek Caban ja...@codeweavers.com: On 01/21/13 13:39, JonY wrote: On 1/21/2013 09:43, Herb Thompson wrote: 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 *__format, __builtin_va_list __local_argv)' as a call to '_vswprintf'. Older versions of msvcrt.dll, like the version in XP SP1, do not include '_vswprintf'. A workaround for this is to compile any C++ libraries and applications that use 'vswprintf' (with the preceding signature) with -D__USE_MINGW_ANSI_STDIO. For example, to build the wxWidgets library for applications to be deployed on XP SP1, build wxWidgets with the following command line: mingw32-make -f makefile.gcc CPPFLAGS=-D__USE_MINGW_ANSI_STDIO Done as https://sourceforge.net/apps/trac/mingw-w64/wiki/_vswprintf%20missing. Thanks. I've also added a caveat section on the side effects of using __USE_MINGW_ANSI_STDIO. Well, IMO we should fix bugs instead of documenting them... I may look at this, but I'm not sure when I will find time for that. Jacek Well, in general I agree. We might should do same hack (for older msvcrt versions) as we do for vscanf (as example). Cheers, Kai Can we do _vswprintf == vswprintf again? And XP SP3 msvcrt.dll doesn't contain _vswprint, too. We must fix it! I'm sorry, I forgot about this before I found the time to fix it. Can you prepare a patch? Thanks, Jacek Same with vsnprintf Index: mingw-w64-crt/lib32/msvcrt.def.in === --- mingw-w64-crt/lib32/msvcrt.def.in(revision 5847) +++ mingw-w64-crt/lib32/msvcrt.def.in(working copy) @@ -1116,7 +1116,7 @@ _vsprintf_p _vsprintf_p_l _vsprintf_s_l -_vswprintf +_vswprintf == vswprintf _vswprintf_c _vswprintf_c_l _vswprintf_l -- Best Regards, xunxun Index: mingw-w64-crt/lib32/msvcrt.def.in === --- mingw-w64-crt/lib32/msvcrt.def.in (revision 5847) +++ mingw-w64-crt/lib32/msvcrt.def.in (working copy) @@ -1116,7 +1116,7 @@ _vsprintf_p _vsprintf_p_l _vsprintf_s_l -_vswprintf +_vswprintf == vswprintf _vswprintf_c _vswprintf_c_l _vswprintf_l -- Learn Graph Databases - Download FREE O'Reilly Book Graph Databases is the definitive new guide to graph databases and their applications. This 200-page book is written by three acclaimed leaders in the field. The early access version is available now. Download your free book today! http://p.sf.net/sfu/neotech_d2d_may___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] Suggestion for FAQ Re _vswprintf and msvcrt.dll on XP SP1
于 2013/1/21 星期一 21:07, Kai Tietz 写道: 2013/1/21 Jacek Caban ja...@codeweavers.com: On 01/21/13 13:39, JonY wrote: On 1/21/2013 09:43, Herb Thompson wrote: 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 *__format, __builtin_va_list __local_argv)' as a call to '_vswprintf'. Older versions of msvcrt.dll, like the version in XP SP1, do not include '_vswprintf'. A workaround for this is to compile any C++ libraries and applications that use 'vswprintf' (with the preceding signature) with -D__USE_MINGW_ANSI_STDIO. For example, to build the wxWidgets library for applications to be deployed on XP SP1, build wxWidgets with the following command line: mingw32-make -f makefile.gcc CPPFLAGS=-D__USE_MINGW_ANSI_STDIO Done as https://sourceforge.net/apps/trac/mingw-w64/wiki/_vswprintf%20missing. Thanks. I've also added a caveat section on the side effects of using __USE_MINGW_ANSI_STDIO. Well, IMO we should fix bugs instead of documenting them... I may look at this, but I'm not sure when I will find time for that. Jacek Well, in general I agree. We might should do same hack (for older msvcrt versions) as we do for vscanf (as example). Cheers, Kai Can we do _vswprintf == vswprintf again? And XP SP3 msvcrt.dll doesn't contain _vswprint, too. We must fix it! -- Best Regards, xunxun -- Learn Graph Databases - Download FREE O'Reilly Book Graph Databases is the definitive new guide to graph databases and their applications. This 200-page book is written by three acclaimed leaders in the field. The early access version is available now. Download your free book today! http://p.sf.net/sfu/neotech_d2d_may ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] Suggestion for FAQ Re _vswprintf and msvcrt.dll on XP SP1
2013/1/23 Xiaofan Chen xiaof...@gmail.com On Wed, Jan 23, 2013 at 2:58 PM, Jim Michaels jmich...@yahoo.com wrote: and, alas, microsoft has made sp2 unavailable and xp next year is support EOL except for embedded. so SP1 users (like me) are out of luck unless they have already downloaded and burned a copy of SP2 and SP3. after EOL, updates will no longer be available from http://windowsupdate.microsoft.com, just like with windows 9x/me/2000. Are you still using Windows XP SP1? If that is the case, I am wondering how you can stop those worms spreading to your computer unless your XP SP1 computer is isolated from the Internet. I still remember the famous W32.Blaster worm affected many university PCs back in 2003. Exactly. I don't see the need for anything to support Windows version whatever past its EOL. That's just a pain the shenanigans with no merit whatsoever. That being said, XP SP1 is stone age, where XP SP3 (!) is more like... iron age. Note this isn't at all the official MinGW-w64 point of view, but my personal opinion on old and deprecated software. Ruben -- Xiaofan -- Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. ON SALE this month only -- learn more at: http://p.sf.net/sfu/learnnow-d2d ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public -- Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. ON SALE this month only -- learn more at: http://p.sf.net/sfu/learnnow-d2d___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] Suggestion for FAQ Re _vswprintf and msvcrt.dll on XP SP1
On Wed, Jan 23, 2013 at 3:22 AM, Ruben Van Boxem wrote: 2013/1/23 Xiaofan Chen On Wed, Jan 23, 2013 at 2:58 PM, Jim Michaels wrote: and, alas, microsoft has made sp2 unavailable and xp next year is support EOL except for embedded. so SP1 users (like me) are out of luck unless they have already downloaded and burned a copy of SP2 and SP3. after EOL, updates will no longer be available from http://windowsupdate.microsoft.com, just like with windows 9x/me/2000. Are you still using Windows XP SP1? If that is the case, I am wondering how you can stop those worms spreading to your computer unless your XP SP1 computer is isolated from the Internet. I still remember the famous W32.Blaster worm affected many university PCs back in 2003. Exactly. I don't see the need for anything to support Windows version whatever past its EOL. That's just a pain the shenanigans with no merit whatsoever. That being said, XP SP1 is stone age, where XP SP3 (!) is more like... iron age. Note this isn't at all the official MinGW-w64 point of view, but my personal opinion on old and deprecated software. Regardless, the header set can be controlled as Microsoft does with NTDDI_VERSION. See http://msdn.microsoft.com/en-us/library/windows/desktop/aa383745(v=vs.85).aspx for reference. In this case NTDDI_VERSION would be = 0x05010300 before _vswprintf is declared. The user would need to set NTDDI_VERSION to the minimum supported value for his software. The user of that software would need to ensure his system meets that minimum standard. -- Earnie -- https://sites.google.com/site/earnieboyd -- Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. ON SALE this month only -- learn more at: http://p.sf.net/sfu/learnnow-d2d ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] Suggestion for FAQ Re _vswprintf and msvcrt.dll on XP SP1
and, alas, microsoft has made sp2 unavailable and xp next year is support EOL except for embedded. so SP1 users (like me) are out of luck unless they have already downloaded and burned a copy of SP2 and SP3. after EOL, updates will no longer be available from http://windowsupdate.microsoft.com, just like with windows 9x/me/2000. http://support.microsoft.com/lifecycle/search/?sort=PNalpha=WINDOWS+XPFilter=FilterNO Jim Michaels From: Kai Tietz ktiet...@googlemail.com To: mingw-w64-public@lists.sourceforge.net Sent: Monday, January 21, 2013 5:07 AM Subject: Re: [Mingw-w64-public] Suggestion for FAQ Re _vswprintf and msvcrt.dll on XP SP1 2013/1/21 Jacek Caban ja...@codeweavers.com: On 01/21/13 13:39, JonY wrote: On 1/21/2013 09:43, Herb Thompson wrote: 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 *__format, __builtin_va_list __local_argv)' as a call to '_vswprintf'. Older versions of msvcrt.dll, like the version in XP SP1, do not include '_vswprintf'. A workaround for this is to compile any C++ libraries and applications that use 'vswprintf' (with the preceding signature) with -D__USE_MINGW_ANSI_STDIO. For example, to build the wxWidgets library for applications to be deployed on XP SP1, build wxWidgets with the following command line: mingw32-make -f makefile.gcc CPPFLAGS=-D__USE_MINGW_ANSI_STDIO Done as https://sourceforge.net/apps/trac/mingw-w64/wiki/_vswprintf%20missing. Thanks. I've also added a caveat section on the side effects of using __USE_MINGW_ANSI_STDIO. Well, IMO we should fix bugs instead of documenting them... I may look at this, but I'm not sure when I will find time for that. Jacek Well, in general I agree. We might should do same hack (for older msvcrt versions) as we do for vscanf (as example). Cheers, Kai -- Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122412 ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public -- Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. ON SALE this month only -- learn more at: http://p.sf.net/sfu/learnnow-d2d___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] Suggestion for FAQ Re _vswprintf and msvcrt.dll on XP SP1
On Wed, Jan 23, 2013 at 2:58 PM, Jim Michaels jmich...@yahoo.com wrote: and, alas, microsoft has made sp2 unavailable and xp next year is support EOL except for embedded. so SP1 users (like me) are out of luck unless they have already downloaded and burned a copy of SP2 and SP3. after EOL, updates will no longer be available from http://windowsupdate.microsoft.com, just like with windows 9x/me/2000. Are you still using Windows XP SP1? If that is the case, I am wondering how you can stop those worms spreading to your computer unless your XP SP1 computer is isolated from the Internet. I still remember the famous W32.Blaster worm affected many university PCs back in 2003. -- Xiaofan -- Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. ON SALE this month only -- learn more at: http://p.sf.net/sfu/learnnow-d2d ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] Suggestion for FAQ Re _vswprintf and msvcrt.dll on XP SP1
On 1/21/2013 09:43, Herb Thompson wrote: 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 *__format, __builtin_va_list __local_argv)' as a call to '_vswprintf'. Older versions of msvcrt.dll, like the version in XP SP1, do not include '_vswprintf'. A workaround for this is to compile any C++ libraries and applications that use 'vswprintf' (with the preceding signature) with -D__USE_MINGW_ANSI_STDIO. For example, to build the wxWidgets library for applications to be deployed on XP SP1, build wxWidgets with the following command line: mingw32-make -f makefile.gcc CPPFLAGS=-D__USE_MINGW_ANSI_STDIO Done as https://sourceforge.net/apps/trac/mingw-w64/wiki/_vswprintf%20missing. Thanks. I've also added a caveat section on the side effects of using __USE_MINGW_ANSI_STDIO. signature.asc Description: OpenPGP digital signature -- Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122412___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] Suggestion for FAQ Re _vswprintf and msvcrt.dll on XP SP1
On 01/21/13 13:39, JonY wrote: On 1/21/2013 09:43, Herb Thompson wrote: 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 *__format, __builtin_va_list __local_argv)' as a call to '_vswprintf'. Older versions of msvcrt.dll, like the version in XP SP1, do not include '_vswprintf'. A workaround for this is to compile any C++ libraries and applications that use 'vswprintf' (with the preceding signature) with -D__USE_MINGW_ANSI_STDIO. For example, to build the wxWidgets library for applications to be deployed on XP SP1, build wxWidgets with the following command line: mingw32-make -f makefile.gcc CPPFLAGS=-D__USE_MINGW_ANSI_STDIO Done as https://sourceforge.net/apps/trac/mingw-w64/wiki/_vswprintf%20missing. Thanks. I've also added a caveat section on the side effects of using __USE_MINGW_ANSI_STDIO. Well, IMO we should fix bugs instead of documenting them... I may look at this, but I'm not sure when I will find time for that. Jacek -- Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122412 ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] Suggestion for FAQ Re _vswprintf and msvcrt.dll on XP SP1
2013/1/21 Jacek Caban ja...@codeweavers.com: On 01/21/13 13:39, JonY wrote: On 1/21/2013 09:43, Herb Thompson wrote: 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 *__format, __builtin_va_list __local_argv)' as a call to '_vswprintf'. Older versions of msvcrt.dll, like the version in XP SP1, do not include '_vswprintf'. A workaround for this is to compile any C++ libraries and applications that use 'vswprintf' (with the preceding signature) with -D__USE_MINGW_ANSI_STDIO. For example, to build the wxWidgets library for applications to be deployed on XP SP1, build wxWidgets with the following command line: mingw32-make -f makefile.gcc CPPFLAGS=-D__USE_MINGW_ANSI_STDIO Done as https://sourceforge.net/apps/trac/mingw-w64/wiki/_vswprintf%20missing. Thanks. I've also added a caveat section on the side effects of using __USE_MINGW_ANSI_STDIO. Well, IMO we should fix bugs instead of documenting them... I may look at this, but I'm not sure when I will find time for that. Jacek Well, in general I agree. We might should do same hack (for older msvcrt versions) as we do for vscanf (as example). Cheers, Kai -- Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122412 ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
