From: Alexey Neyman <stilor@att.net>
To: crossgcc@sourceware.org
Subject: [crosstool-ng/crosstool-ng] 894682: MinGW: add --enable-secure-api config option
Date: Fri, 07 Apr 2017 17:13:00 -0000 [thread overview]
Message-ID: <58e7c8a3f0fa7_1bc93f89c9ef1c34220559@hookshot-fe3-cp1-prd.iad.github.net.mail> (raw)
[-- Attachment #1: Type: text/plain, Size: 1210 bytes --]
Branch: refs/heads/master
Home: https://github.com/crosstool-ng/crosstool-ng
Commit: 89468256ec0d9c63b6ed852a90183e70aecbbe3a
https://github.com/crosstool-ng/crosstool-ng/commit/89468256ec0d9c63b6ed852a90183e70aecbbe3a
Author: Tamir Duberstein <tamird@gmail.com>
Date: 2017-04-06 (Thu, 06 Apr 2017)
Changed paths:
M config/libc/mingw.in
M scripts/build/libc/mingw.sh
Log Message:
-----------
MinGW: add --enable-secure-api config option
Without this flag, MinGW does not expose secure variants of functions
such as strcpy_s.
See https://sourceforge.net/p/mingw-w64/mingw-w64/ci/master/tree/mingw-w64-headers/crt/sec_api/string_s.h#l11.
Commit: 16e703a4e5bc9277ce642d5a7a451c7025d495ad
https://github.com/crosstool-ng/crosstool-ng/commit/16e703a4e5bc9277ce642d5a7a451c7025d495ad
Author: Alexey Neyman <stilor@att.net>
Date: 2017-04-07 (Fri, 07 Apr 2017)
Changed paths:
M config/libc/mingw.in
M scripts/build/libc/mingw.sh
Log Message:
-----------
Merge pull request #676 from tamird/mingw-secure-api
MinGW: add --enable-secure-api config option
Compare: https://github.com/crosstool-ng/crosstool-ng/compare/242c156d95b5...16e703a4e5bc
reply other threads:[~2017-04-07 17:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=58e7c8a3f0fa7_1bc93f89c9ef1c34220559@hookshot-fe3-cp1-prd.iad.github.net.mail \
--to=stilor@att.net \
--cc=crossgcc@sourceware.org \
/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).