search for: mingw_has_secure_api

Janne Hyv?rinen wrote: > Some comments for patch #1, I chose the non-secure versions because they > are faster and produce smaller binary. The functions where these > printings are performed can't in my opinion ever exceed the safety > margin of 32 KB. They print short help and error texts and occasionally > filename, which with APIs is restricted to 260 characters. And you

...nt* the fact that they are safe so you really only > need to look where they are called rather than thinking about maximum > command line lengths and maximum file name lengths. Oops. It seems that vsnprintf_s isn't always available on MinGW platform: MinGW declares this function only if MINGW_HAS_SECURE_API macro is defined. That's because WinXP version of msvcrt.dll doesn't contain secure functions like vsnprintf_s. Maybe it's better to revert vsnprintf_s to vsprintf or to use vnsprintf? (Of course it's also possible to write something like #if defined _MSC_VER || defined MINGW_HA...

lvqcl wrote: > Oops. It seems that vsnprintf_s isn't always available on MinGW platform: > MinGW declares this function only if MINGW_HAS_SECURE_API macro is defined. > That's because WinXP version of msvcrt.dll doesn't contain secure functions > like vsnprintf_s. I thought Micorsoft had recently stopped supporting WinXP. If Micorsoft has stopped supporting it I see no reason for FLAC to support it. Cheers, Erik -- ------------...

lvqcl wrote: > Oops. It seems that vsnprintf_s isn't always available on MinGW platform: > MinGW declares this function only if MINGW_HAS_SECURE_API macro is defined. > That's because WinXP version of msvcrt.dll doesn't contain secure functions > like vsnprintf_s. > > Maybe it's better to revert vsnprintf_s to vsprintf or to use vnsprintf? Ok, we need to drop vsnprintf_s to support WinXP. I'd prefer vsnprintf over...

Erik de Castro Lopo wrote: >> Oops. It seems that vsnprintf_s isn't always available on MinGW platform: >> MinGW declares this function only if MINGW_HAS_SECURE_API macro is defined. >> That's because WinXP version of msvcrt.dll doesn't contain secure functions >> like vsnprintf_s. >> >> Maybe it's better to revert vsnprintf_s to vsprintf or to use vnsprintf? > > Ok, we need to drop vsnprintf_s to support WinXP. I'...

Regarding the earlier mail about [xapian-core-1.2.24] /tests/api_replicate.cc compiled under MSYS/MINGW (g++ 5.3.0). It seems likely that the error was specific to certain g++ versions. https://github.com/mxe/mxe/issues/1448 Eric at ERICS-NETBOOK /c/WORK $ cat test.cpp #include <stdlib.h> int setenv(const char *name, const char *value, int overwrite) { return _putenv_s(name, value); }