public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Ian Lance Taylor <ian@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r13-4416] runtime: force XSI strerror on hurd Date: Wed, 30 Nov 2022 20:21:36 +0000 (GMT) [thread overview] Message-ID: <20221130202136.113693858D1E@sourceware.org> (raw) https://gcc.gnu.org/g:91607eba8fe49c064192122ec60a3e03dd8f2515 commit r13-4416-g91607eba8fe49c064192122ec60a3e03dd8f2515 Author: Ian Lance Taylor <iant@golang.org> Date: Wed Nov 30 09:36:52 2022 -0800 runtime: force XSI strerror on hurd Reviewed-on: https://go-review.googlesource.com/c/gofrontend/+/454275 Diff: --- gcc/go/gofrontend/MERGE | 2 +- libgo/runtime/go-strerror.c | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/gcc/go/gofrontend/MERGE b/gcc/go/gofrontend/MERGE index 984d8324004..a26f779557d 100644 --- a/gcc/go/gofrontend/MERGE +++ b/gcc/go/gofrontend/MERGE @@ -1,4 +1,4 @@ -fef6aa3c1678cdbe7dca454b2cebb369d8ba81bf +1c5bfd57131b68b91d8400bb017f35d416f7aa7b The first line of this file holds the git revision number of the last merge done from the gofrontend repository. diff --git a/libgo/runtime/go-strerror.c b/libgo/runtime/go-strerror.c index 13d1d91df84..8ff5ffbdfec 100644 --- a/libgo/runtime/go-strerror.c +++ b/libgo/runtime/go-strerror.c @@ -12,7 +12,7 @@ exists to selectively undefine it and provides an alias to the XSI-compliant version of strerror_r(3). */ -#ifdef __linux__ +#if defined(__linux__) || defined(__gnu_hurd__) /* Force selection of XSI-compliant strerror_r by glibc. */ #undef XOPEN_SOURCE @@ -21,7 +21,7 @@ #define _POSIX_C_SOURCE 200112L #undef _GNU_SOURCE -#endif /* __linux__ */ +#endif /* defined(__linux__) || defined(__gnu_hurd__) */ #include <string.h>
reply other threads:[~2022-11-30 20:21 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=20221130202136.113693858D1E@sourceware.org \ --to=ian@gcc.gnu.org \ --cc=gcc-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: linkBe 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).