This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: mingw64-*-{headers,runtime,winpthreads}-4.0.5-1(x86/x86_64)
- From: Tony Kelman <tony at kelman dot net>
- To: cygwin at cygwin dot com
- Date: Thu, 17 Mar 2016 08:07:02 +0000 (UTC)
- Subject: Re: mingw64-*-{headers,runtime,winpthreads}-4.0.5-1(x86/x86_64)
- Authentication-results: sourceware.org; auth=none
- References: <announce dot 56DEA4BE dot 30005 at gmail dot com> <BAY169-W74EC22425C0B369EA3DC5AA7B30 at phx dot gbl>
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?
Thanks,
Tony
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple