Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Cc: Jerome Guitton <guitton@adacore.com>
Subject: Re: [RFA] Add --with-curses configure option
Date: Tue, 24 Mar 2009 01:33:00 -0000	[thread overview]
Message-ID: <20090324012742.GN9472@adacore.com> (raw)
In-Reply-To: <20090313020640.GE11284@adacore.com>

> 2009-02-13  Jerome Guitton  <guitton@adacore.com>
> 
>         * configure.ac: Add --with-curses.
>         * configure: Regenerated.

There were no objections, so I checked this patch in after reverifying it
by buiding GDB on x86-linux before the patch (linked to libtermcap.so),
after the patch but without --with-curses (linked to libtermcap.so) and
after the patch using --with-curses (linked to libtermcap.so).

I've also run the regression testsuite, but this time on x86_64-linux
(faster).

I'm trying to decide whether this is worth a NEWS entry or not, and
I am currently leaning towards not. The NEWS file for the upcoming
7.0 release is quite substantial at this point, and I don't want to
dilute it with something that's relatively minor. I checked the
manual too on the section about configuring GDB, and it only describes
the most important command line switches.

So I think it makes sense to not document this feature further.
``configure --help'' shows:

|  --with-curses           use the curses library instead of the termcap
|                          library

-- 
Joel


  reply	other threads:[~2009-03-24  1:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-13  2:21 Joel Brobecker
2009-03-24  1:33 ` Joel Brobecker [this message]
2009-03-24 15:40   ` Jan Kratochvil
2009-03-24 16:13     ` Joel Brobecker
2009-03-24 16:41     ` Jan Kratochvil
2009-03-24 16:57       ` Joel Brobecker
2009-03-24 17:04         ` Jan Kratochvil

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=20090324012742.GN9472@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=guitton@adacore.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