From: Jerry Hidayat <jerry@oncoresystems.com>
To: Momchil Velikov <velco@fadata.bg>
Cc: gdb@sourceware.cygnus.com
Subject: Re: GDB for PowerPC target for cygwin
Date: Wed, 05 Sep 2001 07:22:00 -0000 [thread overview]
Message-ID: <01090509234800.11035@asia> (raw)
In-Reply-To: <m3u1yi5dup.fsf@freon.briz.fadata.bg>
Thanks Velco,
if you can't find strsignal in gdb/defs.h, it means that you are using a
development version of GDB. Thanks anyway.
Jerry
On Wednesday 05 September 2001 01:52, Momchil Velikov wrote:
> >>>>> "Jerry" == Jerry Hidayat <jerry@oncoresystems.com> writes:
>
> Jerry> ******************************************************
> Jerry> In file included from sim_calls.c:43:
> Jerry> ../../gdb/defs.h:51: conflicting types for 'strsignal'
> Jerry> /usr/include/string.h:70: previous declaration of 'strsignal'
> Jerry> make[2]: *** [sim_calls.o] Error 1
> Jerry> make[2]: Leaving directory '/home/paulh/gdb417/gdb-4.17/sim/ppc'
> Jerry> make[1]: *** [all] Error 2
> Jerry> make[1]: Leaving directory '/home/paulh/gdb417/gdb-4.17/sim'
> Jerry> make: *** [all-sim] Error 2
> Jerry> *******************************************************
>
> Jerry> If you guys have any suggestions or ideas what I need to do, please
> help me.
>
> How about upgrading CYGWIN or gdb or both ?
>
> In my c:/cygwin/usr/include/string.h there is
>
> #ifdef __CYGWIN__
> #ifndef DEFS_H /* Kludge to work around problem compiling in gdb */
> const char *_EXFUN(strsignal, (int __signo));
> #endif
> int _EXFUN(strtosigno, (const char *__name));
> #endif
>
> and in gdb/defs.h there is no strsignal at all :-)
>
> Regards,
> -velco
prev parent reply other threads:[~2001-09-05 7:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-04 10:51 Jerry Hidayat
2001-09-04 23:49 ` Momchil Velikov
2001-09-05 7:22 ` Jerry Hidayat [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=01090509234800.11035@asia \
--to=jerry@oncoresystems.com \
--cc=gdb@sourceware.cygnus.com \
--cc=velco@fadata.bg \
/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