- * Notes for BSD/386:
- To compile gdb-4.13 on BSD/386, you must run the configure script and
- its subscripts with bash. Here is an easy way to do this:
-
- bash -c 'CONFIG_SHELL=/bin/bash ./configure'
-
- (configure will report i386-unknown-bsd). Then, compile with the
- standard "make" command.
-
-GDB can produce warnings about symbols that it does not understand. By
-default, these warnings are disabled. You can enable them by executing
-`set complaint 10' (which you can put in your ~/.gdbinit if you like).
-I recommend doing this if you are working on a compiler, assembler,
-linker, or gdb, since it will point out problems that you may be able
-to fix. Warnings produced during symbol reading indicate some mismatch
-between the object file and GDB's symbol reading code. In many cases,
-it's a mismatch between the specs for the object file format, and what
-the compiler actually outputs or the debugger actually understands.
+ * Under Irix 5 for SGIs, you must have installed the `compiler_dev.hdr'
+ subsystem that is on the IDO CD, otherwise you will get complaints
+ that certain files such as `/usr/include/syms.h' cannot be found.
+
+ * Under Irix 6 you must build with GCC. The vendor compiler reports
+ as errors certain assignments that GCC considers to be warnings.
+
+ GDB can produce warnings about symbols that it does not understand.
+By default, these warnings are disabled. You can enable them by
+executing `set complaint 10' (which you can put in your ~/.gdbinit if
+you like). I recommend doing this if you are working on a compiler,
+assembler, linker, or GDB, since it will point out problems that you
+may be able to fix. Warnings produced during symbol reading indicate
+some mismatch between the object file and GDB's symbol reading code.
+In many cases, it's a mismatch between the specs for the object file
+format, and what the compiler actually outputs or the debugger
+actually understands.
+
+
+Graphical interface to GDB -- X Windows, MS Windows
+==========================