This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
[PATCH] Look for cursesX on Ultrix
- From: Mark Kettenis <kettenis at chello dot nl>
- To: gdb-patches at sources dot redhat dot com
- Date: Sun, 8 Aug 2004 00:12:13 +0200 (CEST)
- Subject: [PATCH] Look for cursesX on Ultrix
The normal curses on Ultrix misses functionality we need.
Committed,
Mark
Index: ChangeLog
from Mark Kettenis <kettenis@gnu.org>
* configure.in: Add cursesX to the list of possible curses libs.
Add cursesX.h to the list of possible curses headers.
* configure, config.in: Regenerate.
Index: configure.in
===================================================================
RCS file: /cvs/src/src/gdb/configure.in,v
retrieving revision 1.161
diff -u -p -r1.161 configure.in
--- configure.in 7 Aug 2004 21:52:15 -0000 1.161
+++ configure.in 7 Aug 2004 22:09:53 -0000
@@ -374,7 +374,7 @@ fi
# do anything to look for the matching include files.
# -- chastain 2004-05-01
-AC_SEARCH_LIBS(initscr, [ncurses Hcurses curses pdcurses], [],
+AC_SEARCH_LIBS(initscr, [ncurses Hcurses cursesX curses pdcurses], [],
[AC_MSG_WARN([no curses library found])])
# Check whether the wborder function is provided by the curses
@@ -429,7 +429,7 @@ case $host_os in
Solaris 2.[789] when using GCC. ]])
fi ;;
esac
-AC_CHECK_HEADERS(curses.h ncurses.h term.h)
+AC_CHECK_HEADERS(curses.h cursesX.h ncurses.h term.h)
# FIXME: kettenis/20030102: In most cases we include these
# unconditionally, so what's the point in checking these?