From: Yaakov Selkowitz <yselkowitz@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: tar-1.29 fails to build probably in relation with SSP
Date: Thu, 07 Dec 2017 18:50:00 -0000 [thread overview]
Message-ID: <9e89ea96-cb3a-29f5-1e81-04808732b431@cygwin.com> (raw)
In-Reply-To: <8079FF48-EC42-48BA-9F8B-FEFC47010E50@Denis-Excoffier.org>
[-- Attachment #1.1: Type: text/plain, Size: 974 bytes --]
On 2017-12-06 13:14, Denis Excoffier wrote:
> I have installed the latest snapshot, dated 20171201, which includes the "export SSP functions" commit (dated 20171127).
> I'm also up to date with the packages (gcc 6.4.0 etc.). My uname -a produces:
> CYGWIN_NT-6.1-WOW PC13169 2.10.0(0.323/5/3) i686 Cygwin
>
> I tried to build tar-1.29 and i get several errors, SSP-related i suppose, the first ones being:
[snip]
The builtin SSP implementation does unavoidably conflict with GCC's
inferior one[1], which is the cause of these build errors. When Cygwin
2.10 is released, then GCC will need to be rebuilt without the latter.
If you wish to test _FORTIFY_SOURCE with the current snapshot, then just
move /usr/lib/gcc/$arch-pc-cygwin/6.4.0/include/ssp out of the way.
Note, however, that any binaries so built will require a snapshot DLL at
runtime, and will not run on the 2.9 DLL.
[1] https://sourceware.org/ml/newlib/2017/msg01170.html
--
Yaakov
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2017-12-07 16:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-07 3:17 Denis Excoffier
2017-12-07 18:50 ` Yaakov Selkowitz [this message]
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=9e89ea96-cb3a-29f5-1e81-04808732b431@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).