2003-08-10 Andrew Cagney <cagney@redhat.com>

	* Makefile.in (monitor.o): Do not build monitor.c with -Werror.

diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index 783c6f1..abb7f0d 100644 (file)
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,3 +1,7 @@
+2003-08-10  Andrew Cagney  <cagney@redhat.com>
+
+       * Makefile.in (monitor.o): Do not build monitor.c with -Werror.
+
 2003-08-10  Mark Kettenis  <kettenis@gnu.org>
 
        * i386-tdep.h (i386fbsd_sigtramp_start, i386fbsd_sigtramp_end,

diff --git a/gdb/Makefile.in b/gdb/Makefile.in
index 25d054e..23896f7 100644 (file)
--- a/gdb/Makefile.in
+++ b/gdb/Makefile.in
@@ -1321,6 +1321,15 @@ main.o: main.c
        $(CC) -c $(INTERNAL_CFLAGS) $(TARGET_SYSTEM_ROOT_DEFINE) \
                -DBINDIR=\"$(bindir)\" $(srcdir)/main.c
 
+# FIXME: cagney/2003-08-10: "monitor.c" gets -Wformat-nonliteral
+# errors.  It turns out that that is the least of monitor.c's
+# problems.  The function print_vsprintf appears to be using
+# va_arg(long) to extract CORE_ADDR parameters - something that
+# definitly will not work.  "monitor.c" needs to be rewritten so that
+# it doesn't use format strings and instead uses callbacks.
+monitor.o: $(srcdir)/monitor.c
+       $(CC) -c $(INTERNAL_WARN_CFLAGS) $(NO_WERROR_CFLAGS) $(srcdir)/monitor.c
+
 # FIXME: Procfs.o gets -Wformat errors because things like pid_t don't
 # match output format strings.
 procfs.o: $(srcdir)/procfs.c