Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Tue, 17 Dec 2002 01:17:56 -0500
From: Christopher Faylor <cgf-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: LFTP: cygwin and setupterm
Message-ID: <20021217061756.GB5502@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <29950-220021221753745544 AT M2W028 DOT mail2web DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <29950-220021221753745544@M2W028.mail2web.com>
User-Agent: Mutt/1.5.1i

On Tue, Dec 17, 2002 at 12:37:45AM -0500, elfyn-cygwin AT mail DOT exposure DOT org DOT uk wrote:
>Just checked on both of my servers, they symlink /usr/include/term.h with
>ncurses/term.h, running RedHat 6.1 and 8.0. Should cygwin/ncurses do the
>same?
>
>  The QNX proprietary term_* functions have been deprecated in favor of
>  ncurses. ncurses is a set of terminal-independent routines for painting
>  screens and handling input events......
>
>  .....The file /usr/include/term.h is now an ncurses header file; you'll
>  find the old <term.h> in /usr/include/sys/term.h. An error message is
>  displayed if you combine the old term_* and ncurses header files.

Since the code clearly checks for the situation of finding the needed headers
in /usr/include/ncurses, I don't see any reason why this package should be
used as a justification for adding a symlink.

>Btw, I put the below __CYGWIN__ mention in because it still complained even
>when when it was passed the sufficient defines in CPPFLAGS and CXXFLAGS
>before running configure.

Usually when I see things like HAVE_NCURSES_CURSES_H, it suggests to me
that the author of the source code is correctly attempting to set things
up in a general, non-system-specific way and is testing for various
capabilities and oddities of the operating environment.  System-specific
checks like "#ifdef ultrix" in source quickly become unmanageable.
That's why HAVE_NCURSES_CURSES_H is nice.

There's no reason why it couldn't work in this scenario.  Of course, if it
"complained" maybe all you need to do is rebuke it sternly.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/