From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 127897 invoked by alias); 18 Jan 2018 14:36:24 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 127869 invoked by uid 89); 18 Jan 2018 14:36:23 -0000 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 Received: from limerock04.mail.cornell.edu (HELO limerock04.mail.cornell.edu) (128.84.13.244) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 18 Jan 2018 14:36:22 +0000 X-CornellRouted: This message has been Routed already. Received: from authusersmtp.mail.cornell.edu (granite4.serverfarm.cornell.edu [10.16.197.9]) by limerock04.mail.cornell.edu (8.14.4/8.14.4_cu) with ESMTP id w0IEaKv3000450 for ; Thu, 18 Jan 2018 09:36:20 -0500 Received: from [10.13.22.4] (50-192-26-108-static.hfc.comcastbusiness.net [50.192.26.108]) (authenticated bits=0) by authusersmtp.mail.cornell.edu (8.14.4/8.12.10) with ESMTP id w0IEZwnH001298 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for ; Thu, 18 Jan 2018 09:36:20 -0500 Subject: Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 2.10.0-0.1 To: cygwin@cygwin.com References: <9990d909-f112-9658-1b0f-d63e3f338a18@cornell.edu> From: Ken Brown Message-ID: <4f7edc68-4c98-8fa3-9fef-47bdd3343330@cornell.edu> Date: Thu, 18 Jan 2018 14:36:00 -0000 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 X-SW-Source: 2018-01/txt/msg00172.txt.bz2 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 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