From: Daniel Jacobowitz <drow@false.org>
To: Masaki Muranaka <monaka@monami-software.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Build failed on MinGW host, sh-elf target.
Date: Tue, 16 May 2006 20:23:00 -0000 [thread overview]
Message-ID: <20060516202228.GA13210@nevyn.them.org> (raw)
In-Reply-To: <91ADFB55-F787-4F02-B4EE-C4B3F62CB8AC@monami-software.com>
On Tue, May 16, 2006 at 03:09:20PM +0900, Masaki Muranaka wrote:
> Hello, Daniel.
>
> On 2006/05/16, at 1:58, Daniel Jacobowitz wrote:
> >>2006-05-06 Masaki Muranaka <monaka@monami-software.com>
> >>
> >> * defs.h: Include <time.h> if HAVE_TIME_H is defined.
> >
> >Does this happen anywhere besides ser-e7kpc.c? If not, I would rather
> >add it to just that file.
>
> Hmm... It might be enough to add it to just ser-e7kpc.c.
>
> As far as I built, only ser-e7kpc.c.
> (I built targets m32r-elf, mips64-elf,
> xstormy16-elf, arm-elf, i386-elf, sh-elf,
> m32c-elf, v850-elf, m68k-elf
> on i686-pc-mingw32 host.)
Thanks. I've checked in this, then. Please let us know if you find
more problems!
--
Daniel Jacobowitz
CodeSourcery
2006-05-16 Daniel Jacobowitz <dan@codesourcery.com>
* ser-e7kpc.c: Include <time.h> if it is available.
Index: ser-e7kpc.c
===================================================================
RCS file: /cvs/src/src/gdb/ser-e7kpc.c,v
retrieving revision 1.12
diff -u -p -r1.12 ser-e7kpc.c
--- ser-e7kpc.c 17 Dec 2005 22:34:02 -0000 1.12
+++ ser-e7kpc.c 16 May 2006 20:20:10 -0000
@@ -33,6 +33,10 @@
#include <sys/dos.h>
#endif
+#ifdef HAVE_TIME_H
+#include <time.h>
+#endif
+
static int e7000pc_open (struct serial *scb, const char *name);
static void e7000pc_raw (struct serial *scb);
static int e7000pc_readchar (struct serial *scb, int timeout);
prev parent reply other threads:[~2006-05-16 20:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-06 4:10 Masaki Muranaka
2006-05-15 17:06 ` Daniel Jacobowitz
2006-05-16 6:34 ` Masaki Muranaka
2006-05-16 20:23 ` Daniel Jacobowitz [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=20060516202228.GA13210@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=monaka@monami-software.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