From: Yaakov Selkowitz <yselkowitz@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 2.10.0-0.1
Date: Thu, 18 Jan 2018 21:30:00 -0000 [thread overview]
Message-ID: <3b738a06-a3b8-210b-2886-4c9701efcd48@cygwin.com> (raw)
In-Reply-To: <4f7edc68-4c98-8fa3-9fef-47bdd3343330@cornell.edu>
[-- Attachment #1.1: Type: text/plain, Size: 869 bytes --]
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. 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.
--
Yaakov
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2018-01-18 21:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-16 16:59 Corinna Vinschen
2018-01-17 10:42 ` Houder
2018-01-17 10:50 ` Corinna Vinschen
2018-01-17 11:40 ` Houder
2018-01-17 12:07 ` Houder
2018-01-17 22:29 ` Ken Brown
2018-01-18 14:36 ` Ken Brown
2018-01-18 21:30 ` Yaakov Selkowitz [this message]
2018-01-18 23:28 ` Ken Brown
2018-01-20 3:27 ` Ken Brown
2018-01-20 12:23 ` Ken Brown
2018-01-20 23:49 ` Ken Brown
2018-01-24 19:25 ` Ken Brown
2018-01-25 0:16 ` Yaakov Selkowitz
2018-01-25 2:42 ` Ken Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3b738a06-a3b8-210b-2886-4c9701efcd48@cygwin.com \
--to=yselkowitz@cygwin.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).