From: Ladislav Michl <ladis@linux-mips.org>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] configure.ac: Improve curses searching
Date: Wed, 14 Mar 2012 13:10:44 +0100 [thread overview]
Message-ID: <20120314121044.GA1154@localhost.localdomain> (raw)
In-Reply-To: <20120312085950.GB5487@pengutronix.de>
On Mon, Mar 12, 2012 at 09:59:50AM +0100, Michael Olbrich wrote:
> On Thu, Mar 08, 2012 at 11:07:12AM +0100, Ladislav Michl wrote:
> > This is a resend of an older patch: http://www.mail-archive.com/ptxdist@pengutronix.de/msg03400.html
> >
> > Cygwin-1.7 places curses headers into /usr/include/ncurses.
> > Tested on Debian, MinGW with pdcurses and Cygwin.
>
> any reason, why you changed the search order to look for curses first?
>
> Michael
I'm fine with dropping that change. For mconf, curses is fine. On systems with ncurses,
curses just symlinks to them. Changing order just allows mconf to link to default
curses-type library, whereas ncurses explicitely links to ncurses if it is installed.
ladis
--
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2012-03-14 12:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-08 10:07 Ladislav Michl
2012-03-12 8:59 ` Michael Olbrich
2012-03-14 12:10 ` Ladislav Michl [this message]
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=20120314121044.GA1154@localhost.localdomain \
--to=ladis@linux-mips.org \
--cc=ptxdist@pengutronix.de \
/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