[ANNOUNCEMENT] Updated: mingw64-*-{headers,runtime,winpthreads}-4.0.5-1 (x86/x86_64)

[ANNOUNCEMENT] Updated: mingw64-*-{headers,runtime,winpthreads}-4.0.5-1 (x86/x86_64)

[JonY]

[-- Attachment #1: Type: text/plain, Size: 948 bytes --]

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

The cross compiler can produce Win32 and Win64 native binaries. As a
cross compiler, you may use --host=i686-w64-mingw32 or
--host=x86_64-w64-mingw32 for autotools based source packages to build
for Windows.

              *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO ***

If you want to unsubscribe from the cygwin-announce mailing list, look
at the "List-Unsubscribe: " tag in the email header of this message.
Send email to the address specified there. It will be in the format:

cygwin-announce-unsubscribe-you=yourdomain.com <at> cygwin.com

If you need more information on unsubscribing, start reading here:

http://sourceware.org/lists.html#unsubscribe-simple

Please read *all* of the information on unsubscribing that is available
starting at this URL.



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

RE: [ANNOUNCEMENT] Updated: mingw64-*-{headers,runtime,winpthreads}-4.0.5-1 (x86/x86_64)

[Tony Kelman]

> 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?

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

Re: mingw64-*-{headers,runtime,winpthreads}-4.0.5-1(x86/x86_64)

[Tony Kelman]

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

Re: mingw64-*-{headers,runtime,winpthreads}-4.0.5-1(x86/x86_64)

[JonY]

[-- 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 --]