From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: kettenis@chello.nl, mec.gnu@mindspring.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch] configure.ac, configure: curses/termcap on *-*-osf5.*
Date: Wed, 28 Apr 2004 19:04:00 -0000 [thread overview]
Message-ID: <20040428190459.6F4034B104@berman.michael-chastain.com> (raw)
Mark Kettenis writes:
> What I'm saying is that I don't see why gdb wouldn't build on a
> *-*-osf5* system with a properly installed ncurses if it builds on the
> same system with the vendor's curses library.
Okay, I've tried that. I built ncurses 5.4 from source, built gdb with
it, and it linked and ran. gdbtui opens windows properly.
> What seems to be the problem here is that on the test-drive system
> you're using, the ncurses library isn't properly installed.
That's true, because /usr/local/lib/libncurses.a is missing a lot
of entry points which are described in the locally installed
documentation for ncurses on that system.
> This makes me wonder why configure doesn't detect ncurses as being broken.
configure links a C program with an extern for 'initscr'.
/usr/local/lib/ncurses.a resolves 'initscr' so configure
thinks that the whole library works.
> However, GDB prefers ncurses over the vendor curses library. I think it
> is in the GNU spirit to prefer an Open Source implementation over a
> proprietary one.
Spirit is fine, but we've got actual results from two systems.
The system that Joel uses has no ncurses, and the system that
I use has a broken ncurses. So far nobody has pointed to a system
with a working ncurses.
> The vendor's curses implementation may be incomplete or
> may have serious bugs.
That's true. That's why I actually ran gdbtui after building it
and watched the full-screen version working.
> Could you be so kind to revert the bit of your patch that special
> cases *-*-osf5* when looking for a curses library?
Well, okay. I'll do that.
Michael C
next reply other threads:[~2004-04-28 19:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-28 19:04 Michael Elizabeth Chastain [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-04-28 20:43 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=20040428190459.6F4034B104@berman.michael-chastain.com \
--to=mec.gnu@mindspring.com \
--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