Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: cagney@gnu.org, eliz@elta.co.il
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc] Build TUI when curses
Date: Wed, 11 Feb 2004 15:18:00 -0000	[thread overview]
Message-ID: <20040211151816.7B88F4B104@berman.michael-chastain.com> (raw)

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).

My two cents: it's okay to clean it up, and it's also okay to let it
abort.  It's all good.

Michael C


             reply	other threads:[~2004-02-11 15:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-11 15:18 Michael Elizabeth Chastain [this message]
2004-02-11 15:43 ` Bob Rossi
2004-02-11 15:55   ` Andrew Cagney
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=20040211151816.7B88F4B104@berman.michael-chastain.com \
    --to=mec.gnu@mindspring.com \
    --cc=cagney@gnu.org \
    --cc=eliz@elta.co.il \
    --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