Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: drow@false.org, mec.gnu@mindspring.com
Cc: gdb-patches@sources.redhat.com, kettenis@chello.nl
Subject: Re: [patch] configure.ac, configure: curses/termcap on *-*-osf5.*
Date: Wed, 28 Apr 2004 20:43:00 -0000	[thread overview]
Message-ID: <20040428204406.D30B34B104@berman.michael-chastain.com> (raw)

Daniel Jacobowitz writes:
> That's a mighty deficient ncurses implementation.  Are they in the
> ncurses on your system and not being pulled in?  If they aren't there,
> what IS?

That's a fruitful line of inquiry.

/usr/local/lib/libncurses.a is a version of ncurses 5.2.
But the "tinfo" subdirectory of ncurses has been built as a separate
library, so I have to link gdb with "-lncurses -ltinfo".
This is similar to the situation on hpux where libcur_colr.a is
needed for 'wborder'.

There is another problem.  configure.ac is finding libncurses.a in
/usr/local/lib, but it is not looking for include files in
/usr/local/include.  So gdb is using /usr/include/curses.h at compile
time and /usr/local/lib/libncurses.a at link time.  Fortunately, this
just causes unresolved externals on my particular system.

I worked around *that* problem with "-I /usr/local/include/ncurses".
Now I get a gdbtui that links and runs, but it crashes shortly after
"break main; run; next; next".

Michael C


             reply	other threads:[~2004-04-28 20:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-28 20:43 Michael Elizabeth Chastain [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-04-28 19:04 Michael Elizabeth Chastain
2004-04-28  1:51 Michael Elizabeth Chastain
2004-04-28  2:06 ` Joel Brobecker
2004-04-28  3:58 ` Daniel Jacobowitz
2004-04-28 12:29 ` Mark Kettenis
2004-04-24 11:02 Michael Elizabeth Chastain
2004-04-28  0:13 ` Mark Kettenis

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=20040428204406.D30B34B104@berman.michael-chastain.com \
    --to=mec.gnu@mindspring.com \
    --cc=drow@false.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=kettenis@chello.nl \
    /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