From cfc046cf083b44c6e93cdfbe142767afd5223692 Mon Sep 17 00:00:00 2001 From: Andrew Cagney Date: Thu, 8 Mar 2001 03:19:59 +0000 Subject: [PATCH] Doco SID + GDB + Solaris 8 broken. --- gdb/ChangeLog | 5 +++++ gdb/TODO | 44 ++++++++++++++++---------------------------- 2 files changed, 21 insertions(+), 28 deletions(-) diff --git a/gdb/ChangeLog b/gdb/ChangeLog index 32e592f6a64..264be2b18c8 100644 --- a/gdb/ChangeLog +++ b/gdb/ChangeLog @@ -1,3 +1,8 @@ +2001-03-07 Andrew Cagney + + * TODO (GDB 5.1 Known Problems): Document problem of building GDB + with SID on Solaris 8. + 2001-03-07 Mark Kettenis * defs.h: Provide prototypes for floatformat_is_negative, diff --git a/gdb/TODO b/gdb/TODO index 297171ec881..28bbbe986c5 100644 --- a/gdb/TODO +++ b/gdb/TODO @@ -82,34 +82,6 @@ it keeps coming up :-(. Any volunteers? Mark --- - -Re: GDB 5.0.1? -http://sources.redhat.com/ml/gdb/2000-07/msg00038.html - -Is the Solaris 8 x86 problem fixed? When you configure it, configure -incorrectly determines that I have no curses.h. This causes mucho -compilation errors later on. - -Simply editing the config.h to define CURSES_H fixes the problem, and -then the build works fine. - -The status for this problem: - -Solaris 8 x86 (PIII-560) -gcc 2.95.2 - -I had the same problem with several of the snapshots shortly before -5.0 became official, and 5.0 has the same problem. - -I sent some mail in about it long ago, and never saw a reply. - -I haven't had time to figure it out myself, especially since I get all -confused trying to figure out what configure does, I was happy to find -the workaround. - -Mike - -- GDB 5.1 - New features @@ -250,6 +222,22 @@ z8k The z8k has suffered bit rot and is known to not build. The problem was occuring in the opcodes directory. +-- + +Solaris 8 x86 CURSES_H problem +http://sources.redhat.com/ml/gdb/2000-07/msg00038.html + +The original problem was worked around with: + + 2000-06-06 Michael Snyder + + * configure.in: Enable autoconf to find curses.h on Solaris 2.8. + * configure: Regenerate. + +When building both GDB and SID using the same source tree the problem +will still occure. sid/component/configure.in mis-configures + and leaves wrong information in the config cache. + -- GDB 5.2 - Fixes -- 2.30.2