unittests/offset-type-selftests.c \
unittests/optional-selftests.c \
unittests/ptid-selftests.c \
- unittests/scoped_restore-selftests.c
+ unittests/scoped_restore-selftests.c \
+ unittests/xml-utils-selftests.c
SUBDIR_UNITTESTS_OBS = \
array-view-selftests.o \
offset-type-selftests.o \
optional-selftests.o \
ptid-selftests.o \
- scoped_restore-selftests.o
+ scoped_restore-selftests.o \
+ xml-utils-selftests.o
# Opcodes currently live in one of two places. Either they are in the
# opcode library, typically ../opcodes, or they are in a header file
parse.c \
printcmd.c \
probe.c \
+ producer.c \
proc-service.list \
progspace.c \
progspace-and-thread.c \
print-utils.o \
printcmd.o \
probe.o \
+ producer.o \
progspace.o \
progspace-and-thread.o \
prologue-value.o \
MAKEOVERRIDES =
ALLDEPFILES = \
+ aarch64-fbsd-nat.c \
aarch64-fbsd-tdep.c \
aarch64-linux-nat.c \
aarch64-linux-tdep.c \
# Some files need explicit build rules (due to -Werror problems) or due
# to sub-directory fun 'n' games.
-# 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
- $(COMPILE.pre) $(INTERNAL_CFLAGS) $(GDB_WARN_CFLAGS_NO_FORMAT) \
- $(COMPILE.post) $(srcdir)/monitor.c
- $(POSTCOMPILE)
-
# Do not try to build "printcmd.c" with -Wformat-nonliteral. It manually
# checks format strings.
printcmd.o: $(srcdir)/printcmd.c