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=ytBxmJkCbazpYxoh
	qOOyYHb22loUlKZJURIo26YPVgxK+24yhE7hepHHXwBu6SPBSmCslu2EB2T7DVKU
	MbWovgn8FxjqZMfgf8tJxtGI36mxK6//jNG6YFZjVA+e5M2v7nvbI+Vqfw0gCFd+
	0KE78V+AD1lE89F/LAxELNawFYw=
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=UTIWS2nNpN6KjGlAUVTbd9
	SPe2I=; b=hQsA4fxU9Rb/kr8wguUY5f/6aZvJGPNYxx8roXhGhAAk4zCpSj5j3l
	IF+Kbuq9N4LU/VCyhibsWIfR8RyXOXMHdZdhxDqm649dAQHB7y1ikGy3hnRbw+9X
	3hvxR/004IunFxfabg+h9O6GAVkdAbf9FP/j45ZtQiCtn/MkI59KQ=
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=-0.0 required=5.0 tests=AWL,BAYES_20,KAM_NUMSUBJECT,SPF_HELO_PASS,SPF_PASS,T_RP_MATCHES_RCVD autolearn=no version=3.3.2 spammy=disablelibssp, disable-libssp, 2.10.0, coordinate
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> <4f7edc68-4c98-8fa3-9fef-47bdd3343330 AT cornell DOT edu> <3b738a06-a3b8-210b-2886-4c9701efcd48 AT cygwin DOT com>
From:	Ken Brown <kbrown AT cornell DOT edu>
Message-ID:	<eb4e6cf2-12aa-bb4c-738e-f2259f58f3fe@cornell.edu>
Date:	Thu, 18 Jan 2018 18:28:39 -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:	<3b738a06-a3b8-210b-2886-4c9701efcd48@cygwin.com>
X-PMX-Cornell-Gauge:	Gauge=XX
X-PMX-CORNELL-AUTH-RESULTS:	dkim-out=none;
X-IsSubscribed:	yes

On 1/18/2018 4:30 PM, Yaakov Selkowitz wrote:
> On 2018-01-18 08:35, Ken Brown wrote:
>> On 1/17/2018 5:29 PM, Ken Brown wrote:
>>> Do we need a new gcc release to go along with the recent ssp changes?
>>
>> The following commit message seems to answer my question:
>>
>>      Note that this does require building gcc with --disable-libssp and
>>      gcc_cv_libc_provides_ssp=yes.
> 
> Correct.
> 
>> 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?
> 
> -D_FORTIFY_SOURCE is not the default, so simply omitting it is
> sufficient.

I was talking about building projects in which _FORTIFY_SOURCE is 
defined by default.  That happens, for instance, in the gnulib 
subdirectory of the emacs tree, so it may affect other projects that use 
gnulib also.

> You could also just delete
> /usr/lib/gcc/*-pc-cygwin/6.4.0/include/ssp, since we won't need it
> anymore and it wasn't even being used properly in the first place.

That's a simpler workaround than what I was doing.  Thanks.

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

- Raw text -