This is the mail archive of the cygwin mailing list for the Cygwin project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On 3/17/2016 16:07, Tony Kelman wrote: > Tony Kelman <tony <at> kelman.net> writes: > >> >>> I have just updated the mingw-w64 headers, runtime, and winpthreads to >>> 4.0.5-1. >>> >>> mingw64-*-headers-4.0.5-1 >>> mingw64-*-runtime-4.0.5-1 >>> mingw64-*-winpthreads-4.0.5-1 >> >> Question, since I just had issues building some of LLVM's unit tests and >> tracked the root cause back to here - is it intentional that x86_64-headers >> gets built with --enable-secure-api but i686-headers doesn't? > > Week later, hopefully socially acceptable ping. Can I request that > mingw64-i686-headers get rebuilt with --enable-secure-api at the next > update? Is there an especially good reason not to have it enabled by > default? > Sorry, I didn't notice your email. No, its an oversight, a new v4.x update will be coming soon, it should have this fixed.
Attachment:
signature.asc
Description: OpenPGP digital signature
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |