public inbox for libstdc++-cvs@sourceware.org
help / color / mirror / Atom feed
From: Jonathan Wakely <redi@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org
Subject: [gcc r13-3684] libstdc++: Define _GNU_SOURCE for secure_getenv on Cygwin [PR107511]
Date: Fri,  4 Nov 2022 14:05:50 +0000 (GMT)	[thread overview]
Message-ID: <20221104140550.60D60381D455@sourceware.org> (raw)

https://gcc.gnu.org/g:f505f37a8e5a7646af4038b5c46f72d8a05dc7f0

commit r13-3684-gf505f37a8e5a7646af4038b5c46f72d8a05dc7f0
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Thu Nov 3 11:44:47 2022 +0000

    libstdc++: Define _GNU_SOURCE for secure_getenv on Cygwin [PR107511]
    
    As in r12-6867-ge20486d508afdf we need to define _GNU_SOURCE explicitly
    for Cygwin, because configure finds it in libc but it isn't declared
    unless we request it.
    
    libstdc++-v3/ChangeLog:
    
            PR libstdc++/107511
            * libsupc++/eh_alloc.cc (_GNU_SOURCE): Define.

Diff:
---
 libstdc++-v3/libsupc++/eh_alloc.cc | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/libstdc++-v3/libsupc++/eh_alloc.cc b/libstdc++-v3/libsupc++/eh_alloc.cc
index e93f14c887b..83d15f39ca4 100644
--- a/libstdc++-v3/libsupc++/eh_alloc.cc
+++ b/libstdc++-v3/libsupc++/eh_alloc.cc
@@ -25,6 +25,11 @@
 // This is derived from the C++ ABI for IA-64.  Where we diverge
 // for cross-architecture compatibility are noted with "@@@".
 
+#ifndef _GNU_SOURCE
+// Cygwin needs this for secure_getenv
+# define _GNU_SOURCE 1
+#endif
+
 #include <exception>           // std::exception
 #include <new>                 // std::terminate
 #include <cstdlib>             // std::malloc, std::free, std::strtoul

                 reply	other threads:[~2022-11-04 14:05 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=20221104140550.60D60381D455@sourceware.org \
    --to=redi@gcc.gnu.org \
    --cc=gcc-cvs@gcc.gnu.org \
    --cc=libstdc++-cvs@gcc.gnu.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).