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=F9BCmAGqCrxotHp9
	tPxjHQDEELsOF631pXZQhIp2+k/33sibGNT9Qu3xEPXcGOtmnHkzJU0/KlKznn5M
	HAcOlCRAkyzEZoLGjdB0HiZ9iI+NfEUrE98o5HzSgdczq2RjPo4wgkgbTPhE74wx
	rxs+uW7E6ZOTDKZybptaFy/+8qg=
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=ILGc4/jXUX2MdLqkKM1Qz3
	LEVqk=; b=cXIHwybK8a7S5TdmHnim/e/JHPRtFh6/OmtkGl23spizTSRSNBav0/
	oSLxceGPpi9d0h4AH4uncEnEG48bJA5+09k9PlEKBmaNoT8gj96ggpZPMat1U0gS
	KyGfiTKUS1SdZR7mOSHDdSj8yKnldnToebhX4MKjm4TYiDgQmH5og=
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.1 required=5.0 tests=AWL,BAYES_40,KAM_NUMSUBJECT,SPF_HELO_PASS,SPF_PASS,T_RP_MATCHES_RCVD autolearn=no version=3.3.2 spammy=disablelibssp, disable-libssp, sk:gcc_cv_, 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> <eb4e6cf2-12aa-bb4c-738e-f2259f58f3fe AT cornell DOT edu>
From: Ken Brown <kbrown AT cornell DOT edu>
Message-ID: <c5a92ae1-3b63-0227-f170-fa1d0ac959eb@cornell.edu>
Date: Fri, 19 Jan 2018 22:27:43 -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: <eb4e6cf2-12aa-bb4c-738e-f2259f58f3fe@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
Note-from-DJ: This may be spam

On 1/18/2018 6:28 PM, Ken Brown wrote:
> 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.

Here's another issue that's come up with _FORTIFY_SOURCE.  One of the 
emacs source files, fileio.c, makes use of a pointer to readlinkat. 
[More precisely, the file uses an external function foo() with a 
parameter 'bar' that's a pointer to a function; foo is called in 
fileio.c with bar = readlinkat.]

When _FORTIFY_SOURCE > 0, this leads to an "undefined reference to 
`__ssp_protected_readlinkat'" linking error.  Does this sound like 
something that will be fixed with the new gcc release?

I realize I haven't given you full details, but it might be a few days 
until I have a chance to extract an STC for this issue, so I thought I'd 
give it a shot.

If you can't answer the question based on the information above, I'll 
make an STC as soon as I can.

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