Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: Daniel Jacobowitz <drow@mvista.com>, "Martin M. Hunt" <hunt@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] fix for utils.c bool problem
Date: Thu, 07 Feb 2002 14:01:00 -0000	[thread overview]
Message-ID: <3C62F941.90805@cygnus.com> (raw)
In-Reply-To: <20020207163944.A30605@nevyn.them.org>

Martin,



@@ -20,18 +20,18 @@
    Foundation, Inc., 59 Temple Place - Suite 330,
    Boston, MA 02111-1307, USA.  */
 
-#include "defs.h"
-#include "gdb_assert.h"
-#include <ctype.h>
-#include "gdb_string.h"
-#include "event-top.h"
-
 #ifdef HAVE_CURSES_H
 #include <curses.h>
#endif
 #ifdef HAVE_TERM_H
 #include <term.h>
#endif
+
+#include "defs.h"
+#include "gdb_assert.h"
+#include <ctype.h>
+#include "gdb_string.h"
+#include "event-top.h"
 
 #ifdef __GO32__
 #include <pc.h>

It needs to at least include "config.h" first (that is where HAVE_CURSES_H is defined).  I think something like:


#include "config.h"
#include "bfd.h"
#include "defs.h"

but the ``I think'' highlights the problem :-(  I don't think we should 
be working around problems in an un released BFD :-/

Andrew




  reply	other threads:[~2002-02-07 22:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-07 13:33 Martin M. Hunt
2002-02-07 13:39 ` Daniel Jacobowitz
2002-02-07 14:01   ` Andrew Cagney [this message]
2002-02-07 14:14     ` Daniel Jacobowitz
2002-02-07 15:28       ` Andrew Cagney
2002-02-08  7:57   ` Daniel Jacobowitz
2002-02-08  8:51     ` Andrew Cagney
2002-02-08  8:57       ` Daniel Jacobowitz
2002-02-08  9:09         ` Andrew Cagney
2002-02-08  9:38           ` Daniel Jacobowitz
2002-02-08 10:55             ` Andrew Cagney
2002-02-28 22:04               ` Andrew Cagney
2002-02-07 13:40 ` Fernando Nasser

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3C62F941.90805@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=drow@mvista.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=hunt@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox