summaryrefslogtreecommitdiffstats
path: root/gdb/config/vax/xm-vaxult.h
diff options
context:
space:
mode:
Diffstat (limited to 'gdb/config/vax/xm-vaxult.h')
-rw-r--r--gdb/config/vax/xm-vaxult.h12
1 files changed, 12 insertions, 0 deletions
diff --git a/gdb/config/vax/xm-vaxult.h b/gdb/config/vax/xm-vaxult.h
new file mode 100644
index 0000000000..24c6437060
--- /dev/null
+++ b/gdb/config/vax/xm-vaxult.h
@@ -0,0 +1,12 @@
+/* Definitions to make GDB run on a vax under Ultrix. */
+
+#include "vax/xm-vax.h"
+extern char *strdup();
+
+/* 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
OpenPOWER on IntegriCloud