X-Recipient: archive-cygwin AT delorie DOT com
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=DfHB5htqx7Hrl17G
	PTeYeNbxrW1AMfoaFP+Y7IvjSR2w0vSj+C7LgUNRRIGXVGTW5KntLeDtV4OwVNFU
	lc7P0sjOTS9LbEMphB2wTbMCsMLTb5znJFXkzmVO9l2JBfNFKq3ntfT/xwTCW3b+
	cXEOMS8JMh9dMuNitGiDr2ANPZs=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; 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; s=default; bh=rjXxh/PTjITRCHkSTNPrCL
	um6hQ=; b=V3qMdK9EJixbrAD0p9SAaUQUE8COsD9cuJVtcS/V1cGqssuozeAcdD
	CMy/BW6d6fQfqmIPXmJkMEDnFUYwy0scphwThs6e3hOP3ZeHoCpdWUVITt8DoZDr
	osDnNcTBGHMXpBjNy6yMyC/LF3Kv33WeJ/2tDnioEUSe2MuiUg9AA=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00,KAM_NUMSUBJECT,SPF_HELO_PASS,SPF_PASS,T_RP_MATCHES_RCVD autolearn=no version=3.3.2 spammy=meantime, Hx-languages-length:933, Ken, disablelibssp
X-HELO: limerock04.mail.cornell.edu
X-CornellRouted: This message has been Routed already.
Subject: Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 2.10.0-0.1
To: cygwin AT cygwin DOT com
References: <announce DOT 20180116155108 DOT GA9503 AT calimero DOT vinschen DOT de> <9990d909-f112-9658-1b0f-d63e3f338a18 AT cornell DOT edu>
From: Ken Brown <kbrown AT cornell DOT edu>
Message-ID: <4f7edc68-4c98-8fa3-9fef-47bdd3343330@cornell.edu>
Date: Thu, 18 Jan 2018 09:35:52 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2
MIME-Version: 1.0
In-Reply-To: <9990d909-f112-9658-1b0f-d63e3f338a18@cornell.edu>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
X-PMX-Cornell-Gauge: Gauge=XX
X-PMX-CORNELL-AUTH-RESULTS: dkim-out=none;
X-IsSubscribed: yes

On 1/17/2018 5:29 PM, Ken Brown wrote:
> On 1/16/2018 10:51 AM, Corinna Vinschen wrote:
>> Hi folks,
>>
>>
>> I uploaded a new Cygwin test release 2.10.0-0.1
>>
>> I'm planning for a release end of January.  Please test.
> 
> Do we need a new gcc release to go along with the recent ssp changes?

The following commit message seems to answer my question:

commit 3e8fc7d9f21329d5a98ec3cf6de138bce9bc2c05
Author: Yaakov Selkowitz <yselkowi AT redhat DOT com>
Date:   Mon Nov 27 23:07:10 2017 -0600

     ssp: add Object Size Checking common code

[...]

     Note that this does require building gcc with --disable-libssp and
     gcc_cv_libc_provides_ssp=yes.


Are there plans to coordinate the release of Cygwin 2.10.0 with a new 
gcc release?  In the meantime, I guess package maintainers have to build 
with -U_FORTIFY_SOURCE in order to test building with Cygwin 2.10.0.  Or 
am I missing something?

Ken

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