From: Andrew Cagney <cagney@gnu.org>
To: Bob Rossi <bob@brasko.net>,
Michael Elizabeth Chastain <mec.gnu@mindspring.com>
Cc: eliz@elta.co.il, gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc] Build TUI when curses
Date: Wed, 11 Feb 2004 15:55:00 -0000 [thread overview]
Message-ID: <402A5082.5000502@gnu.org> (raw)
In-Reply-To: <20040211154331.GC2395@white>
> On Wed, Feb 11, 2004 at 10:18:16AM -0500, Michael Elizabeth Chastain wrote:
>
>> If there is no curses library, then readline won't build, so it's okay
>> for gdb to require curses as well (until someone reorganizes gdb so that
>> it can be built without readline).
>
>
> Are you sure readline requires curses to build?
>
> This is in readline's ./configure --help
> Optional Packages:
> --with-curses use the curses library instead of the termcap
> library
>
> Also, this is from readline's INSTALL file,
>
> `--with-curses'
> This tells readline that it can find the termcap library functions
> (tgetent, et al.) in the curses library, rather than a separate
> termcap library. Readline uses the termcap functions, but does not
> link with the termcap or curses library itself, allowing applications
> which link with readline the to choose an appropriate library.
> This option tells readline to link the example programs with the
> curses library rather than libtermcap.
That matches my reading of GDB's configure.in (look for "termcap").
Andrew
next prev parent reply other threads:[~2004-02-11 15:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-11 15:18 Michael Elizabeth Chastain
2004-02-11 15:43 ` Bob Rossi
2004-02-11 15:55 ` Andrew Cagney [this message]
2004-02-11 19:26 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2004-02-11 15:58 Michael Elizabeth Chastain
2004-02-10 20:10 Andrew Cagney
2004-02-11 6:38 ` Eli Zaretskii
2004-02-11 14:52 ` Andrew Cagney
2004-02-16 19:36 ` Andrew Cagney
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=402A5082.5000502@gnu.org \
--to=cagney@gnu.org \
--cc=bob@brasko.net \
--cc=eliz@elta.co.il \
--cc=gdb-patches@sources.redhat.com \
--cc=mec.gnu@mindspring.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