DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=LHhFVKrVr5UtCcKm
	tuDXV2VmK+EGu/y8H7vUssRDX0lMEMTESa/0Nx7mc9VmvZAIMD3zxOCkRpZ0y9NT
	B+GXgPkrdYXoxVmjj+WdvocanHaYzu82g4PyWgoDOw+O50eZdlN4jTSJdtg7EQf/
	Oq4A0Das8bo5iIGPcJ++LEsLpfU=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Subject: Re: No thread safety in clock_gettime (hires_ns::prime)
To: cygwin@cygwin.com
References: <CAOWZHxdJi1E9APtSXm35LkDU33VqGZSwnGtvOfdHA9PTTJgRjQ@mail.gmail.com> <20181126170140.GO30649@calimero.vinschen.de>
From: cyg Simple <cygsimple@gmail.com>
Message-ID: <b75436b1-848a-bb22-670a-3ae32baadd62@gmail.com>
Date: Mon, 26 Nov 2018 12:34:33 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.3.1
MIME-Version: 1.0
In-Reply-To: <20181126170140.GO30649@calimero.vinschen.de>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

On 11/26/2018 12:01 PM, Corinna Vinschen wrote:
> On Nov 23 11:27, James E. King III wrote:
>> Using 32-bit cygwin that I set up yesterday.
> 
> Don't do that.  Use 64 bit Cygwin whenever possible.  32 bit is a lost
> cause.
> 

When exactly will it be a lost cause for Cygwin?  I.E. Are you planning 
to discontinue maintenance for 32bit anytime soon?  Anyone needing it 
could continue to use the existing distribution.  I ask only because I 
agree with your statement that it is a lost cause.

-- 
cyg Simple

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