Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <kettenis@chello.nl>
To: brobecker@gnat.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [hppa] GDB doesn't build with tui
Date: Mon, 23 Feb 2004 21:14:00 -0000	[thread overview]
Message-ID: <200402232114.i1NLEBnH000310@elgar.kettenis.dyndns.org> (raw)
In-Reply-To: <20040223200513.GF1273@gnat.com> (message from Joel Brobecker on Mon, 23 Feb 2004 12:05:13 -0800)

   Date: Mon, 23 Feb 2004 12:05:13 -0800
   From: Joel Brobecker <brobecker@gnat.com>

   Hello,

   GDB no longer builds on HP/UX 11.00 since TUI is built in by default.
   The obvious work-around is to configure GDB --without-tui.

i386-*-solaris2.9 fails for the same reason.  Here the problem is that
the header files are broken when _SYCALL32 is defined.  I'm working on
a solution.

   The error we get is during the link: the wborder symbol is undefined.

   This triggers a question: Which version of curses are we planning on
   supporting. For instance, on our machine, we currently have the system
   curses library. Do we intend to support the system curses libraries,
   or only say ncurses?

HP-UX has several curses libs: Hcurses, Xcurses?

   (BTW: it's bizarre to see that 'man wborder' on HP/UX reveals that it
   thinks that this function is defined, and then we can even see it
   in /usr/include/curses.h - albeit protected by a #ifdef -, but then
   the symbol is missing from /usr/lib/libcurses.1... Will have a look,
   but I'm not familiar with curses).

It's even more bizarre, since the TUI was contributed by HP.

Mark


  reply	other threads:[~2004-02-23 21:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-23 20:05 Joel Brobecker
2004-02-23 21:14 ` Mark Kettenis [this message]
2004-02-23 21:27   ` Joel Brobecker
2004-02-23 23:26     ` 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=200402232114.i1NLEBnH000310@elgar.kettenis.dyndns.org \
    --to=kettenis@chello.nl \
    --cc=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