Re: [Mingw-w64-public] [Patch] Add memmove_s emu

2014-07-31 Thread JonY
On 7/31/2014 17:16, Dongsheng Song wrote: > This commit broken the gcc 4.9 building: > > $ make > make all-am > make[1]: Entering directory > `/home/cauchy/obj/x86_64-w64-mingw32-gcc-4.9/mingw-w64-crt' > make[1]: *** No rule to make target `secapi/memmove_s.c', needed by > `secapi/lib64_libmsvcrt

Re: [Mingw-w64-public] [Patch] Add memmove_s emu

2014-07-31 Thread Dongsheng Song
This commit broken the gcc 4.9 building: $ make make all-am make[1]: Entering directory `/home/cauchy/obj/x86_64-w64-mingw32-gcc-4.9/mingw-w64-crt' make[1]: *** No rule to make target `secapi/memmove_s.c', needed by `secapi/lib64_libmsvcrt_a-memmove_s.o'. Stop. make[1]: Leaving directory `/home/

Re: [Mingw-w64-public] [Patch] Add memmove_s emu

2014-07-30 Thread JonY
On 7/29/2014 04:04, Ruben De Smet wrote: > Some applications, like CryptoPP, won't run on Windows XP, because > memmove_s isn't defined in that OS. As I needed CryptoPP to compile > easily, I wrote this patch. It emulates the method by checking for the > availability and falling back on memmove (wi

[Mingw-w64-public] [Patch] Add memmove_s emu

2014-07-29 Thread Ruben De Smet
Some applications, like CryptoPP, won't run on Windows XP, because memmove_s isn't defined in that OS. As I needed CryptoPP to compile easily, I wrote this patch. It emulates the method by checking for the availability and falling back on memmove (without s). I mimicked memcpy_s. I'm not subscrib