Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <kettenis@chello.nl>
To: brobecker@gnat.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Fix i386v-nat.c compilation
Date: Fri, 25 Oct 2002 14:24:00 -0000	[thread overview]
Message-ID: <200210252124.g9PLO4SP036930@elgar.kettenis.dyndns.org> (raw)
In-Reply-To: <20021025202934.GF4370@gnat.com> (message from Joel Brobecker on Fri, 25 Oct 2002 13:29:34 -0700)

   Date: Fri, 25 Oct 2002 13:29:34 -0700
   From: Joel Brobecker <brobecker@gnat.com>

   > Index: ChangeLog
   > from  Mark Kettenis  <kettenis@gnu.org>
   > 
   > 	* i386v-nat.c: Include "i386-tdep.h".

   I think that Makefile.in should be updated too: Add $(i386_tdep_h) to
   the rule for i386v-nat.o.

Oops.  Fixed with the attached patch.

Index: ChangeLog
from  Mark Kettenis  <kettenis@gnu.org>

	* Makefile.in (i386v-nat.o): Add $(i386_tdep_h).

Index: Makefile.in
===================================================================
RCS file: /cvs/src/src/gdb/Makefile.in,v
retrieving revision 1.272
diff -u -p -r1.272 Makefile.in
--- Makefile.in 24 Oct 2002 00:13:57 -0000 1.272
+++ Makefile.in 25 Oct 2002 21:12:54 -0000
@@ -1763,7 +1763,7 @@ i386obsd-nat.o: i386obsd-nat.c $(defs_h)
 i386obsd-tdep.o: i386obsd-tdep.c $(defs_h) $(arch_utils_h) $(gdbcore_h) \
 	$(regcache_h) $(i386_tdep_h) $(i387_tdep_h)
 i386v-nat.o: i386v-nat.c $(defs_h) $(frame_h) $(inferior_h) $(language_h) \
-	$(gdbcore_h) $(gdb_stat_h) $(floatformat_h) $(target_h)
+	$(gdbcore_h) $(gdb_stat_h) $(floatformat_h) $(target_h) $(i386_tdep_h)
 i386v4-nat.o: i386v4-nat.c $(defs_h) $(value_h) $(inferior_h) $(regcache_h) \
 	$(i386_tdep_h) $(i387_tdep_h) $(gregset_h)
 i387-tdep.o: i387-tdep.c $(defs_h) $(frame_h) $(inferior_h) $(language_h) \


      reply	other threads:[~2002-10-25 21:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-25 11:55 Mark Kettenis
2002-10-25 13:28 ` Joel Brobecker
2002-10-25 14:24   ` Mark Kettenis [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=200210252124.g9PLO4SP036930@elgar.kettenis.dyndns.org \
    --to=kettenis@chello.nl \
    --cc=brobecker@gnat.com \
    --cc=gdb-patches@sources.redhat.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