Re: [Mingw-w64-public] _FORTIFY_SOURCE support ?

2019-08-25 Thread Christian Franke
JonY wrote: On 8/24/19 6:50 PM, Christian Franke wrote: Hi, packages from Linux and *BSD distros are often build with -D_FORTIFY_SOURCE=2 set by default. This enables buffer overflow checks for functions like strcpy() if buffer size is known at compile time. Attached is an experimental patch t

Re: [Mingw-w64-public] _FORTIFY_SOURCE support ?

2019-08-25 Thread JonY via Mingw-w64-public
On 8/24/19 6:50 PM, Christian Franke wrote: > Hi, > > packages from Linux and *BSD distros are often build with > -D_FORTIFY_SOURCE=2 set by default. This enables buffer overflow checks > for functions like strcpy() if buffer size is known at compile time. > > Attached is an experimental patch th

Re: [Mingw-w64-public] _FILE_OFFSET_BITS on 64-bit systems

2019-08-25 Thread Liu Hao
在 2019/8/25 23:14, LRN 写道: > The way i read _mingw_stat64.h and sys/stat.h, if _FILE_OFFSET_BITS is > undefined (i.e. autotools is not being used) and the host architecture is > x86_64, we end up with struct stat that has 32-bit st_size field, because > _off_t is always 32-bit, and there's no macro

[Mingw-w64-public] _FILE_OFFSET_BITS on 64-bit systems

2019-08-25 Thread LRN
The way i read _mingw_stat64.h and sys/stat.h, if _FILE_OFFSET_BITS is undefined (i.e. autotools is not being used) and the host architecture is x86_64, we end up with struct stat that has 32-bit st_size field, because _off_t is always 32-bit, and there's no macro to turn stat into _stat64, because