From: Christian Biesinger <cbiesinger@google.com>
To: newlib@sourceware.org
Subject: Re: [PATCH] Unconditionally declare strsignal
Date: Tue, 26 Oct 2021 15:35:59 -0400 [thread overview]
Message-ID: <CAPTJ0XG9vSJtFUkd+xm-WoEj4g1Uj+NOCjB1Q6qB4L+BFXqYfA@mail.gmail.com> (raw)
In-Reply-To: <20211008194654.627119-1-cbiesinger@google.com>
Ping?
On Fri, Oct 8, 2021 at 3:46 PM Christian Biesinger
<cbiesinger@google.com> wrote:
>
> Currently, newlib does not declare strsignal if DEFS_H is defined,
> ostensibly to work around a gdb bug. However, gdb itself compiles
> even with this ifndef removed, and this makes sim (another part of
> gdb) fail to compile.
>
> Since it is not clear exactly what issue this was working around,
> this patch just removes that ifndef.
> ---
> newlib/libc/include/string.h | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/newlib/libc/include/string.h b/newlib/libc/include/string.h
> index 60e837bc0..ec74b10d5 100644
> --- a/newlib/libc/include/string.h
> +++ b/newlib/libc/include/string.h
> @@ -130,9 +130,7 @@ char *strlwr (char *);
> char *strupr (char *);
> #endif
>
> -#ifndef DEFS_H /* Kludge to work around problem compiling in gdb */
> char *strsignal (int __signo);
> -#endif
>
> #ifdef __CYGWIN__
> int strtosigno (const char *__name);
> --
> 2.33.0.882.g93a45727a2-goog
>
next prev parent reply other threads:[~2021-10-26 19:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-08 19:46 Christian Biesinger
2021-10-09 1:15 ` Mike Frysinger
2021-10-26 19:35 ` Christian Biesinger [this message]
2021-10-26 19:47 ` Corinna Vinschen
2021-10-27 16:41 ` [PATCH v2] " Christian Biesinger
2021-10-27 18:07 ` Corinna Vinschen
2021-10-27 16:42 ` [PATCH] " Christian Biesinger
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=CAPTJ0XG9vSJtFUkd+xm-WoEj4g1Uj+NOCjB1Q6qB4L+BFXqYfA@mail.gmail.com \
--to=cbiesinger@google.com \
--cc=newlib@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).