From: Andrew Cagney <cagney@gnu.org>
To: Michael Elizabeth Chastain <mec.gnu@mindspring.com>
Cc: kettenis@chello.nl, gdb-patches@sources.redhat.com
Subject: Re: [patch] configure.in: revert osf5.1 no-noncurses special case
Date: Fri, 07 May 2004 15:51:00 -0000 [thread overview]
Message-ID: <409BB064.2030209@gnu.org> (raw)
In-Reply-To: <20040507151048.CA6424B104@berman.michael-chastain.com>
> 4A. if --with-ncurses is not specified, always use curses
> 4B. if --with-ncurses is not specified, probe for ncurses automatically anyways
Is it --with-curses=.... more correct? Anything in autoconf 2.5x to
handle this?
Andrew
next prev parent reply other threads:[~2004-05-07 15:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-07 15:10 Michael Elizabeth Chastain
2004-05-07 15:33 ` Daniel Jacobowitz
2004-05-07 16:19 ` Mark Kettenis
2004-05-07 16:49 ` Daniel Jacobowitz
2004-05-07 15:51 ` Andrew Cagney [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-05-08 0:11 Michael Elizabeth Chastain
2004-05-08 15:58 ` Daniel Jacobowitz
2004-05-07 17:05 Michael Elizabeth Chastain
2004-05-07 15:52 Michael Elizabeth Chastain
2004-05-07 16:23 ` Mark Kettenis
2004-05-07 16:45 ` Daniel Jacobowitz
2004-05-01 22:27 Michael Elizabeth Chastain
2004-05-07 13:50 ` 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=409BB064.2030209@gnu.org \
--to=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=kettenis@chello.nl \
--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