Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@gnat.com>
To: gdb-patches@sources.redhat.com
Subject: [RFA/RFC] (hppa/tui) Fix build failure due to missing wborder
Date: Mon, 23 Feb 2004 22:03:00 -0000	[thread overview]
Message-ID: <20040223220334.GH1273@gnat.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 594 bytes --]

Hello,

Re: http://sources.redhat.com/ml/gdb-patches/2004-02/msg00654.html

On HP/UX, the GDB build fails during the link due to a missing wborder.
I found the symbol in libcur_colr.sl. To fix the build, I suggest the
following change, although I could conceive that this is not the best
way of handling this. Comments and suggestions warmly welcome.

2004-02-23  J. Brobecker  <brobecker@gnat.com>

        * configure.in (LIBS): Add -lcur_colr when TUI is enabled and
        when using the HP curses library.
        * configure: Regenerate.

Tested on HP/UX 11.00, and x86-linux.

-- 
Joel

[-- Attachment #2: configure.in.diff --]
[-- Type: text/plain, Size: 1831 bytes --]

Index: configure.in
===================================================================
RCS file: /cvs/src/src/gdb/configure.in,v
retrieving revision 1.147
diff -u -2 -0 -r1.147 configure.in
--- configure.in	18 Feb 2004 19:01:36 -0000	1.147
+++ configure.in	23 Feb 2004 21:49:25 -0000
@@ -150,40 +150,45 @@
 AC_ARG_ENABLE(tui,
 [  --enable-tui            enable full-screen terminal user interface (TUI)],
   [case $enableval in
     yes | no)
       ;;
     *)
       AC_MSG_ERROR([bad value $enableval for --enable-tui]) ;;
   esac],enable_tui=yes)
 if test x"$enable_tui" = xyes; then
   if test -d $srcdir/tui; then
     if test "$ac_cv_search_initscr" != no; then
       CONFIG_OBS="$CONFIG_OBS \$(SUBDIR_TUI_OBS)"
       CONFIG_DEPS="$CONFIG_DEPS \$(SUBDIR_TUI_DEPS)"
       CONFIG_SRCS="$CONFIG_SRCS \$(SUBDIR_TUI_SRCS)"
       CONFIG_INITS="$CONFIG_INITS \$(SUBDIR_TUI_INITS)"
       ENABLE_CFLAGS="$ENABLE_CFLAGS \$(SUBDIR_TUI_CFLAGS)"
       CONFIG_ALL="${CONFIG_ALL} all-tui"
       CONFIG_CLEAN="${CONFIG_CLEAN} clean-tui"
       CONFIG_INSTALL="${CONFIG_INSTALL} install-tui"
       CONFIG_UNINSTALL="${CONFIG_UNINSTALL} uninstall-tui"
+      if test "$ac_cv_search_initscr" = "-lHcurses"; then
+        # Hcurses does not provide all of curses. Certain functions
+        # such as wborder for instance are provided by libcur_colr.
+        LIBS="$LIBS -lcur_colr"
+      fi
     fi
   fi
 fi
 
 # Enable gdbtk.
 AC_ARG_ENABLE(gdbtk,
 [  --enable-gdbtk          enable gdbtk graphical user interface (GUI)],
   [case $enableval in
     yes | no)
       ;;
     *)
       AC_MSG_ERROR([bad value $enableval for --enable-gdbtk]) ;;
   esac],
   [if test -d $srcdir/gdbtk; then
     enable_gdbtk=yes
   else
     enable_gdbtk=no
   fi])
 # We unconditionally disable gdbtk tests on selected platforms.
 case $host_os in

             reply	other threads:[~2004-02-23 22:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-23 22:03 Joel Brobecker [this message]
2004-02-24 23:34 ` Andrew Cagney
2004-02-25  1:18   ` Joel Brobecker
2004-02-25  2:09     ` Daniel Jacobowitz
2004-02-25 18:59       ` Joel Brobecker
2004-02-25 19:55         ` Andrew Cagney
2004-02-25 20:11           ` Joel Brobecker
2004-02-25 20:30         ` Mark Kettenis
2004-02-26  0:43           ` Joel Brobecker

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=20040223220334.GH1273@gnat.com \
    --to=brobecker@gnat.com \
    --cc=gdb-patches@sources.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