From: Jim Kingdon Date: Tue, 24 Aug 1993 15:23:23 +0000 (+0000) Subject: * config/vax/xm-vaxult.h: Define NO_PTRACE_H. X-Git-Url: http://drtracing.org/?a=commitdiff_plain;h=0e646bd577e26032cac72cea5d3d2111930098fe;p=deliverable%2Fbinutils-gdb.git * config/vax/xm-vaxult.h: Define NO_PTRACE_H. --- diff --git a/gdb/ChangeLog b/gdb/ChangeLog index 19e68807f9..ac560a4e8f 100644 --- a/gdb/ChangeLog +++ b/gdb/ChangeLog @@ -1,5 +1,7 @@ Tue Aug 24 00:36:17 1993 Jim Kingdon (kingdon@lioth.cygnus.com) + * config/vax/xm-vaxult.h: Define NO_PTRACE_H. + * target.c, target.h: Add "set remotedebug" command. * remote-bug.c, remote.c, remote-mips.c: Remove "set remotedebug" and "set m88ksnoop" options and use generic "set remotedebug" instead. diff --git a/gdb/config/vax/xm-vaxult.h b/gdb/config/vax/xm-vaxult.h index 3bc4f275c9..20fd3685f8 100644 --- a/gdb/config/vax/xm-vaxult.h +++ b/gdb/config/vax/xm-vaxult.h @@ -4,3 +4,11 @@ extern char *strdup(); #define MEM_FNS_DECLARED + +/* This is required for Ultrix 3.1b, not for later versions. Ultrix + 3.1b can't just use xm-vaxult2.h because Ultrix 3.1b does define + FD_SET. Sure, we could have separate configurations for vaxult2, + vaxult3, and vaxult, but why bother? Defining the ptrace constants + in infptrace.c isn't going to do any harm; it's not like they are + going to change. */ +#define NO_PTRACE_H