Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org
Subject: [rfa] Add a prototype for tgetnum
Date: Thu, 23 Feb 2006 18:35:00 -0000	[thread overview]
Message-ID: <20060223183224.GA30924@nevyn.them.org> (raw)

Right now a Win32 GDB fails to build because of the tgetnum ("li") call
in utils.c.  This patch parallels why it works for readline, which doesn't
get a warning.

Does anyone object?

-- 
Daniel Jacobowitz
CodeSourcery

2006-02-23  Daniel Jacobowitz  <dan@codesourcery.com>

	* gdb_curses.h: Provide a fallback prototype for tgetnum.

Index: src/gdb/gdb_curses.h
===================================================================
--- src.orig/gdb/gdb_curses.h	2006-02-23 11:40:05.000000000 -0500
+++ src/gdb/gdb_curses.h	2006-02-23 13:29:43.000000000 -0500
@@ -1,6 +1,6 @@
 /* Portable <curses.h>.
 
-   Copyright (C) 2004 Free Software Foundation, Inc.
+   Copyright (C) 2004, 2006 Free Software Foundation, Inc.
 
    This file is part of GDB.
 
@@ -36,6 +36,12 @@
 #include <ncurses/term.h>
 #elif defined (HAVE_TERM_H)
 #include <term.h>
+#else
+/* On MinGW, a real termcap library is usually not present.  Stub versions
+   of the termcap functions will be built from win32-termcap.c.  Readline
+   provides its own extern declarations when there's no termcap.h; do the
+   same here for the termcap functions used in GDB.  */
+extern int tgetnum (const char *);
 #endif
 
 #endif /* gdb_curses.h */


             reply	other threads:[~2006-02-23 18:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-23 18:35 Daniel Jacobowitz [this message]
2006-02-23 20:18 ` Mark Kettenis
2006-02-23 21:00   ` Daniel Jacobowitz
2006-02-24  8:38 ` Eli Zaretskii

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=20060223183224.GA30924@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    /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