From: JonY <10walls@gmail.com>
To: cygwin@cygwin.com
Subject: Re: mingw64-*-{headers,runtime,winpthreads}-4.0.5-1(x86/x86_64)
Date: Thu, 17 Mar 2016 10:28:00 -0000 [thread overview]
Message-ID: <56EA86C2.9080600@gmail.com> (raw)
In-Reply-To: <loom.20160317T090346-49@post.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 883 bytes --]
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 #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
prev parent reply other threads:[~2016-03-17 10:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-08 10:23 [ANNOUNCEMENT] Updated: mingw64-*-{headers,runtime,winpthreads}-4.0.5-1 (x86/x86_64) JonY
2016-03-09 7:31 ` Tony Kelman
2016-03-17 8:07 ` mingw64-*-{headers,runtime,winpthreads}-4.0.5-1(x86/x86_64) Tony Kelman
2016-03-17 10:28 ` JonY [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56EA86C2.9080600@gmail.com \
--to=10walls@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).