public inbox for gdbadmin@sourceware.org help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com> To: "Claudius Schnörr" <schnoerr@mailzone.com> Cc: gdbadmin@sourceware.org, brobecker@adacore.com Subject: Re: Bugreport for binutils-gdb on cygwin Date: Mon, 18 Oct 2021 12:01:36 -0700 [thread overview] Message-ID: <20211018190136.GD3549@adacore.com> (raw) In-Reply-To: <bbc14129-453a-506f-ce0a-e24c1afcfcbf@mailzone.com> Hello Claudius, > I write to you since I don't know where to submit a bugreport. > After trying to compile the insight gdb-frontent on cygwin > (git://sourceware.org/git/insight.git) the maintainer classified the > following issue to directly be addressed to binutils-gdb package: Personally, I unfortunately do not have much knowledge about cygwin (I know a little bit about MinGW-w64, but not cygwin). So I can't even tell whether cygwin implements the strsignal function or not. I think your best bet is if you can send the information you sent us to the GDB community at gdb-patches@sourceware.org instead. This is a good and easily understandable description of the issue you are facing, and perhaps there will be someone who knows enough about Cygwin to suggest a path forward, and in particular guide you towards fixing the problem and perhaps even submitting a patch. Another option is to perhaps contact the cygwin community to see if they have any information about that function. In particular, whether or not that function is available on cygwin platforms or not. You can try to report the issue on our bugzilla: https://sourceware.org/bugzilla/enter_bug.cgi?product=gdb > * platform: > o cygwin 64bit on Win-10 > o gcc (GCC) 11.2.0, g++ (GCC) 11.2.0 > > * commands submitted: > o git clone --recursive git://sourceware.org/git/binutils-gdb.git > o autoconf > o ./configure > o make > > * Error message: > o event-top.c: In function ‘void handle_fatal_signal(int)’: > event-top.c:893:18: error: ‘strsignal’ was not declared in this > scope; did you mean ‘strsigno’? > 893 | sig_write (strsignal (sig)); > > * comment: > o strsignal() is declared in string.h. However, including it > doesn't work. > Then I inspected string.h on cygwin64 in /usr/include and found > this: > o #ifndef DEFS_H /* Kludge to work around problem compiling in > gdb */ > char *strsignal (int __signo); > #endif > o suggestion: undefining DEFS_H might be risky -> to be added at > line 55: > + #ifndef DEFS_H > # include <string.h> /* for strsignal on > cygwin */ > #else > char *strsignal (int __signo); /* see > /usr/include/string.h on cygwin */ > #endif > o then it compiles, however a library is missed now: > + x86_64-pc-cygwin/bin/ld: > event-top.o:.../insight/bundle/gdb/event-top.c:899: > undefined reference to `strsignal(int)' > collect2: error: ld returned 1 exit status > > Hope this helps somehow. > > Kind regards, > > Claudius > > -- Joel
prev parent reply other threads:[~2021-10-18 19:01 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-16 16:12 Claudius Schnörr 2021-10-18 19:01 ` Joel Brobecker [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=20211018190136.GD3549@adacore.com \ --to=brobecker@adacore.com \ --cc=gdbadmin@sourceware.org \ --cc=schnoerr@mailzone.com \ /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).