From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
To: <gdb-patches@sourceware.org>
Cc: "'Pedro Alves'" <pedro@codesourcery.com>,
"'Stan Shebs'" <stan@codesourcery.com>
Subject: [RFA] Fix mingw32 gdbserver build failure
Date: Tue, 15 Jun 2010 10:06:00 -0000 [thread overview]
Message-ID: <001201cb0c72$5c2b55a0$148200e0$@muller@ics-cnrs.unistra.fr> (raw)
gdbserver compilation fails for mingw32.
This was because of int64_t use in emit_const
of revision 1.70 dated 2010-06-14.
Rather than simply adding a single line patch as obvious,
I would prefer that we use HAVE_STDINT_H
in all occurences of include <stdint.h>
Pierre Muller
ChangeLog entry:
2010-06-15 Pierre Muller <muller@ics.u-strasbg.fr>
* server.h: Add missing "stdint.h" include with guard.
thread-db.c: Add inlcude guard for "stdint.h" header.
Index: server.h
===================================================================
RCS file: /cvs/src/src/gdb/gdbserver/server.h,v
retrieving revision 1.70
diff -u -p -r1.70 server.h
--- server.h 14 Jun 2010 22:16:09 -0000 1.70
+++ server.h 15 Jun 2010 09:56:57 -0000
@@ -29,6 +29,9 @@
#include <stdarg.h>
#include <stdio.h>
#include <stdlib.h>
+#ifdef HAVE_STDINT_H
+#include <stdint.h>
+#endif
#ifdef HAVE_ERRNO_H
#include <errno.h>
#endif
Index: thread-db.c
===================================================================
RCS file: /cvs/src/src/gdb/gdbserver/thread-db.c,v
retrieving revision 1.36
diff -u -p -r1.36 thread-db.c
--- thread-db.c 3 May 2010 18:13:36 -0000 1.36
+++ thread-db.c 15 Jun 2010 09:56:57 -0000
@@ -34,7 +34,9 @@ static int thread_db_use_events;
#include <dlfcn.h>
#endif
+#ifdef HAVE_STDINT_H
#include <stdint.h>
+#endif
#include <limits.h>
#include <ctype.h>
next reply other threads:[~2010-06-15 10:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-15 10:06 Pierre Muller [this message]
2010-06-15 10:40 ` Pedro Alves
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='001201cb0c72$5c2b55a0$148200e0$@muller@ics-cnrs.unistra.fr' \
--to=pierre.muller@ics-cnrs.unistra.fr \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.com \
--cc=stan@codesourcery.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: 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