Exactly for such cases we add emulation-code to our libmingwex.a. To have it within the .def file for msvcrt is for sure nothing we want. Instead we should add an emulation-code for it, as we did already for other such functions. See in our crt the sec_api folder.
Regards, Kai 2016-01-09 18:33 GMT+01:00 Roger Pack <rogerdpa...@gmail.com>: > On 12/29/15, lh_mouse <lh_mo...@126.com> wrote: >> That was because the 'libmsvcrt.a' library was created using a new version >> of MSVCRT.DLL which exported the function, but the MSVCRT.DLL shipped with >> Windows XP didn't. > > Yes, I guess the question is (currently the default mechanism can > present executables that don't work on XP, because configure cannot > easily detect the absence of vsnprintf_s) is this desired? Or if that > ship has sailed, that's OK too. > -roger- > > ------------------------------------------------------------------------------ > Site24x7 APM Insight: Get Deep Visibility into Application Performance > APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month > Monitor end-to-end web transactions and take corrective actions now > Troubleshoot faster and improve end-user experience. Signup Now! > http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140 > _______________________________________________ > Mingw-w64-public mailing list > Mingw-w64-public@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/mingw-w64-public ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140 _______________________________________________ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
