Re: LFTP: cygwin and setupterm

Re: LFTP: cygwin and setupterm

[elfyn-cygwin]

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.


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.

Elfyn
elfyn@exposure.org.uk

Original Message:
-----------------
From: Christopher Faylor cgf-cygwin@cygwin.com
Date: Mon, 16 Dec 2002 23:46:30 -0500
To: cygwin@cygwin.com
Subject: Re: LFTP: cygwin and setupterm


On Tue, Dec 17, 2002 at 02:12:54AM -0300, Fr?d?ric L. W. Meunier wrote:
>
...
>>
>> #if defined(__CYGWIN__)
>> # include <ncurses/term.h>
>> # include <curses.h>
>> #elif defined(HAVE_CURSES_H)
>> # include <curses.h>
>> # if defined(HAVE_TERM_H)
>> #  include <term.h>
>> # endif
>> #elif defined(HAVE_NCURSES_CURSES_H)
>> #include <ncurses/curses.h>
>> # if defined(HAVE_NCURSES_TERM_H)
>> #  include <ncurses/term.h>
>> # endif
>> #endif
>>
...

Why is there a separate Cygwin definition there at at all?  It seems
like everything should be handled by HAVE_NCURSES_CURSES_H and
HAVE_NCURSES_TERM_H.  Either that or the #if for the HAVE_NCURSES_TERM_H
should be moved outside of the if for HAVE_NCURSES_CURSES_H.

Btw, I just checked and uninstalling the termcap package (assuming
this is what you mean) does not install /usr/include/term.h.  That's
not a file which is included in the termcap distribution.

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/

--------------------------------------------------------------------
mail2web - Check your email from the web at
http://mail2web.com/ .



--
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/

Re: LFTP: cygwin and setupterm

[Christopher Faylor]

On Tue, Dec 17, 2002 at 12:37:45AM -0500, elfyn-cygwin@mail.exposure.org.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/

Re: [ANNOUNCEMENT] Updated: gcc-mingw-20020817-3

[Jim]

Thank you.

--
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/

Re: [ANNOUNCEMENT] Updated: gcc-mingw-20020817-3

[Christopher Faylor]

On Tue, Dec 17, 2002 at 06:47:20AM -0800, Jim wrote:
>Thank you.

For what?  I'm still mystified as to why you didn't download
this package to begin with or at least reinstall it as suggested.

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/

Re: LFTP: Cygwin and setupterm

[Charles Wilson]

This thread has a lot of misinformation and just plain confusion.

For starters, term.h != termcap.h.  Some messages in this thread talk 
about term.h, others about termcap.h -- and seem to mean one when 
they're talking about the other.  Sigh.

Also, /usr/include/termcap.h is NOT the ncurses version (on a stock 
cygwin system).  The ncurses termcap compatibility header file is 
/usr/include/ncurses/termcapn.h (note the extra 'n')

No, the standard ncurses package doesn't put a term.h -> ncurses/term.h 
symlink.  It probably should; my linux box includes these symlinks that 
the ncurses cygwin package doesn't:
   /usr/include/term.h -> ncurses/term.h
   /usr/include/eti.h  -> ncurses/eti.h
For now, do it yourself.  I've added this change to my ncurses TODO 
list, so the next ncurses release will do this for you.

As far as Frederic's problem goes, I'd create the new symlinks, and 
re-run configure (after deleting config.cache).  Hopefully that will 
make the changes to lftp_tinfo.cc unnecessary.

-----------------------------------------------------
[[ ONLY for the brave; NO FURTHER support for this variant will be 
forthcoming ]]
If you want to use ncurses as a complete replacement for libtermcap 
(when compiling; this procedure will NOT change the runtime behavior of 
already-compiled programs), then you need to:
   rename
     /usr/include/ncurses/termcapn.h to
     /usr/include/ncurses/termcap.h
Do NOT copy it into /usr/include -- the "real" termcap.h should live 
there.  [DON'T DO THIS: You'd want to uninstall the termcap package BUT 
YOU CAN'T].  The problem is, the termcap package includes the header and 
library *as well as* /etc/termcap.   You want to keep /etc/termcap; so 
you must manually delete /usr/include/termcap.h, /usr/lib/libtermcap.a, 
and /usr/man/man3/termcap.3.   And they'll reappear the next time you 
update the termcap package.

Once you've done all this, if the package you are compiling is set up 
properly, it will see termcap.h in /usr/include/ncurses, and use it (and 
will automatically link using -lcurses or -lncurses instead of 
-ltermcap.  But only if your autoconfigury stuff is handled properly. 
If it is not, then it's a bug in the package you're trying to compile -- 
go talk to them about it.
-----------------------------------------------------

--Chuck

Frédéric L. W. Meunier wrote:
> On Mon, 16 Dec 2002, elfyn-cygwin@mail.exposure.org.uk wrote:
> 
> 
>>The setupterm() function lives in the ncurses package
>>(/usr/include/ncurses/term.h). The problem happens in the if pre-processor
>>clause on line 26 of lftp_tinfo.cc. I got around that by changing the order
>>and switching an if to an elif statement like this:
>>
>>#if defined(__CYGWIN__)
>># include <ncurses/term.h>
>># include <curses.h>
>>#elif defined(HAVE_CURSES_H)
>># include <curses.h>
>># if defined(HAVE_TERM_H)
>>#  include <term.h>
>># endif
>>#elif defined(HAVE_NCURSES_CURSES_H)
>>#include <ncurses/curses.h>
>># if defined(HAVE_NCURSES_TERM_H)
>>#  include <ncurses/term.h>
>># endif
>>#endif
>>
>>May not have been the right thing to do but got past that
>>problem. Now I got a `undefined reference to `_WinMain@16''
>>error, probably because I dont have libsup++ installed
>>though.
> 
> 
> I don't have libsupc++. I'm using the latest gcc2.
> 
> I think the right fix was to make the /usr/include/term.h
> symlink, which for some reason:
> 
> 1- Isn't in ncurses 5.2-8
> or
> 2- Is removed when you uninstall libtermcap
> 



--
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/

Re: LFTP: cygwin and setupterm

[Christopher Faylor]

On Tue, Dec 17, 2002 at 02:12:54AM -0300, Fr?d?ric L. W. Meunier wrote:
>On Mon, 16 Dec 2002, elfyn-cygwin@mail.exposure.org.uk wrote:
>> The setupterm() function lives in the ncurses package
>> (/usr/include/ncurses/term.h). The problem happens in the if pre-processor
>> clause on line 26 of lftp_tinfo.cc. I got around that by changing the order
>> and switching an if to an elif statement like this:
>>
>> #if defined(__CYGWIN__)
>> # include <ncurses/term.h>
>> # include <curses.h>
>> #elif defined(HAVE_CURSES_H)
>> # include <curses.h>
>> # if defined(HAVE_TERM_H)
>> #  include <term.h>
>> # endif
>> #elif defined(HAVE_NCURSES_CURSES_H)
>> #include <ncurses/curses.h>
>> # if defined(HAVE_NCURSES_TERM_H)
>> #  include <ncurses/term.h>
>> # endif
>> #endif
>>
>> May not have been the right thing to do but got past that
>> problem. Now I got a `undefined reference to `_WinMain@16''
>> error, probably because I dont have libsup++ installed
>> though.
>
>I don't have libsupc++. I'm using the latest gcc2.
>
>I think the right fix was to make the /usr/include/term.h
>symlink, which for some reason:
>
>1- Isn't in ncurses 5.2-8
>or
>2- Is removed when you uninstall libtermcap

Why is there a separate Cygwin definition there at at all?  It seems
like everything should be handled by HAVE_NCURSES_CURSES_H and
HAVE_NCURSES_TERM_H.  Either that or the #if for the HAVE_NCURSES_TERM_H
should be moved outside of the if for HAVE_NCURSES_CURSES_H.

Btw, I just checked and uninstalling the termcap package (assuming
this is what you mean) does not install /usr/include/term.h.  That's
not a file which is included in the termcap distribution.

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/

RE: LFTP: Cygwin and setupterm

[Frédéric L. W. Meunier]

On Mon, 16 Dec 2002, elfyn-cygwin@mail.exposure.org.uk wrote:

> May not have been the right thing to do but got past that
> problem.

Actually I think you and Larry are right. What would happen if
I had /usr/include/termcap.h from libtermcap and not ncurses ?
I don't think LFTP or anything should mix headers.

I have the same setup on Linux. No libtermcap (it's a symlink
to libncurses), though I made the /usr/include/termcap.h
symlink. It's probably right to have the symlink if libtermcap
isn't installed.

-- 
0@pervalidus.{net, {dyndns.}org}


--
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/

RE: LFTP: Cygwin and setupterm

[Frédéric L. W. Meunier]

On Mon, 16 Dec 2002, elfyn-cygwin@mail.exposure.org.uk wrote:

> The setupterm() function lives in the ncurses package
> (/usr/include/ncurses/term.h). The problem happens in the if pre-processor
> clause on line 26 of lftp_tinfo.cc. I got around that by changing the order
> and switching an if to an elif statement like this:
>
> #if defined(__CYGWIN__)
> # include <ncurses/term.h>
> # include <curses.h>
> #elif defined(HAVE_CURSES_H)
> # include <curses.h>
> # if defined(HAVE_TERM_H)
> #  include <term.h>
> # endif
> #elif defined(HAVE_NCURSES_CURSES_H)
> #include <ncurses/curses.h>
> # if defined(HAVE_NCURSES_TERM_H)
> #  include <ncurses/term.h>
> # endif
> #endif
>
> May not have been the right thing to do but got past that
> problem. Now I got a `undefined reference to `_WinMain@16''
> error, probably because I dont have libsup++ installed
> though.

I don't have libsupc++. I'm using the latest gcc2.

I think the right fix was to make the /usr/include/term.h
symlink, which for some reason:

1- Isn't in ncurses 5.2-8
or
2- Is removed when you uninstall libtermcap

-- 
0@pervalidus.{net, {dyndns.}org}


--
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/

Re: LFTP: Cygwin and setupterm

[Larry Hall (RFK Partners, Inc)]

At 11:46 PM 12/16/2002, Frédéric L. W. Meunier wrote:
>On Mon, 16 Dec 2002, Larry Hall (RFK Partners, Inc) wrote:
>
> > At 11:03 PM 12/16/2002, Frédéric L. W. Meunier wrote:
> > >Anybody know what's wrong ? I tried to compile LFTP 2.6.3 with
> > >ncurses 5.2-8 and got the following:
> > >
> > >/cygdrive/g/Linux/lftp/src/lftp_tinfo.cc: In function `void init_terminfo()':
> > >/cygdrive/g/Linux/lftp/src/lftp_tinfo.cc:50: implicit declaration of function `int setupterm(...)'
> > >
> > >There's the following in lftp_tinfo.cc:
> > >
> > >#if defined(HAVE_TIGETSTR)
> > >static bool terminfo_ok = true;
> > >static void init_terminfo()
> > >{
> > >    static bool initted = false;
> > >    if(initted) return;
> > >    initted = true;
> > >
> > >    int errret=0;
> > >    if(setupterm(NULL, 1, &errret) == ERR)
> > >       terminfo_ok = false;
> > >}
> > >#endif
> > >
> > >The same error someone reported some time ago with 2.6.2:
> > >
> > >http://www.mail-archive.com/lftp@uniyar.ac.ru/msg00888.html
> > >
> > >I also e-mailed the lftp-devel mailing-list.
> >
> >
> >
> > This is a trick question, right?  I mean, you know how to
> > search for a prototype in the system include directories
> > don't you?  I'm assuming that you have a real question here
> > but I can't figure out what it is. Can you enlighten us/me?
>
>Sorry, I just found
>http://sources.redhat.com/ml/cygwin/2002-10/msg00122.html
>
>I had to make the symlink (I thought it'd be in ncurses) and
>run configure again, since just typing make isn't enough.


Actually sounds to me like this a configuration issue for LFTP.
I don't think a change to ncurses should be necessary to make
LFTP build.  It seems to me that this would be a problem on 
other platforms using ncurses as well if that were the case.


>I can't reproduce the other problem reported by George Lefter.


Good! :-)


Larry Hall                              lhall@rfk.com
RFK Partners, Inc.                      http://www.rfk.com
838 Washington Street                   (508) 893-9779 - RFK Office
Holliston, MA 01746                     (508) 893-9889 - FAX


--
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/

RE: LFTP: Cygwin and setupterm

[elfyn-cygwin]

Hi,

The setupterm() function lives in the ncurses package
(/usr/include/ncurses/term.h). The problem happens in the if pre-processor
clause on line 26 of lftp_tinfo.cc. I got around that by changing the order
and switching an if to an elif statement like this:

#if defined(__CYGWIN__)
# include <ncurses/term.h>
# include <curses.h>
#elif defined(HAVE_CURSES_H)
# include <curses.h>
# if defined(HAVE_TERM_H)
#  include <term.h>
# endif
#elif defined(HAVE_NCURSES_CURSES_H)
#include <ncurses/curses.h>
# if defined(HAVE_NCURSES_TERM_H)
#  include <ncurses/term.h>
# endif
#endif

May not have been the right thing to do but got past that problem. Now I
got a `undefined reference to `_WinMain@16'' error, probably because I dont
have libsup++ installed though.

Elfyn
elfyn@exposure.org.uk

Original Message:
-----------------
From: Frédéric L. W. Meunier 0@pervalidus.net
Date: Tue, 17 Dec 2002 01:03:13 -0300 (E. South America Standard Time)
To: cygwin@cygwin.com
Subject: LFTP: Cygwin and setupterm


Anybody know what's wrong ? I tried to compile LFTP 2.6.3 with
ncurses 5.2-8 and got the following:

/cygdrive/g/Linux/lftp/src/lftp_tinfo.cc: In function `void
init_terminfo()':
/cygdrive/g/Linux/lftp/src/lftp_tinfo.cc:50: implicit declaration of
function `int setupterm(...)'

There's the following in lftp_tinfo.cc:

#if defined(HAVE_TIGETSTR)
static bool terminfo_ok = true;
static void init_terminfo()
{
   static bool initted = false;
   if(initted) return;
   initted = true;

   int errret=0;
   if(setupterm(NULL, 1, &errret) == ERR)
      terminfo_ok = false;
}
#endif

The same error someone reported some time ago with 2.6.2:

http://www.mail-archive.com/lftp@uniyar.ac.ru/msg00888.html

I also e-mailed the lftp-devel mailing-list.

-- 
0@pervalidus.{net, {dyndns.}org}


--
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/

--------------------------------------------------------------------
mail2web - Check your email from the web at
http://mail2web.com/ .



--
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/

Re: LFTP: Cygwin and setupterm

[Frédéric L. W. Meunier]

On Mon, 16 Dec 2002, Larry Hall (RFK Partners, Inc) wrote:

> At 11:03 PM 12/16/2002, Frédéric L. W. Meunier wrote:
> >Anybody know what's wrong ? I tried to compile LFTP 2.6.3 with
> >ncurses 5.2-8 and got the following:
> >
> >/cygdrive/g/Linux/lftp/src/lftp_tinfo.cc: In function `void init_terminfo()':
> >/cygdrive/g/Linux/lftp/src/lftp_tinfo.cc:50: implicit declaration of function `int setupterm(...)'
> >
> >There's the following in lftp_tinfo.cc:
> >
> >#if defined(HAVE_TIGETSTR)
> >static bool terminfo_ok = true;
> >static void init_terminfo()
> >{
> >    static bool initted = false;
> >    if(initted) return;
> >    initted = true;
> >
> >    int errret=0;
> >    if(setupterm(NULL, 1, &errret) == ERR)
> >       terminfo_ok = false;
> >}
> >#endif
> >
> >The same error someone reported some time ago with 2.6.2:
> >
> >http://www.mail-archive.com/lftp@uniyar.ac.ru/msg00888.html
> >
> >I also e-mailed the lftp-devel mailing-list.
>
>
>
> This is a trick question, right?  I mean, you know how to
> search for a prototype in the system include directories
> don't you?  I'm assuming that you have a real question here
> but I can't figure out what it is. Can you enlighten us/me?

Sorry, I just found
http://sources.redhat.com/ml/cygwin/2002-10/msg00122.html

I had to make the symlink (I thought it'd be in ncurses) and
run configure again, since just typing make isn't enough.

I can't reproduce the other problem reported by George Lefter.

I configured with --disable-dependency-tracking --disable-nls
--disable-static

I'm C'cing lftp-devel so that others know the answer in case
they have the same problem.

> BTW, the answer to Joe's question that you reference above is
> "No, setupterm() is not supposed to be part of libc
> (libcygwin.a).

-- 
0@pervalidus.{net, {dyndns.}org}


--
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/

Re: LFTP: Cygwin and setupterm

[Larry Hall (RFK Partners, Inc)]

At 11:03 PM 12/16/2002, Frédéric L. W. Meunier wrote:
>Anybody know what's wrong ? I tried to compile LFTP 2.6.3 with
>ncurses 5.2-8 and got the following:
>
>/cygdrive/g/Linux/lftp/src/lftp_tinfo.cc: In function `void init_terminfo()':
>/cygdrive/g/Linux/lftp/src/lftp_tinfo.cc:50: implicit declaration of function `int setupterm(...)'
>
>There's the following in lftp_tinfo.cc:
>
>#if defined(HAVE_TIGETSTR)
>static bool terminfo_ok = true;
>static void init_terminfo()
>{
>    static bool initted = false;
>    if(initted) return;
>    initted = true;
>
>    int errret=0;
>    if(setupterm(NULL, 1, &errret) == ERR)
>       terminfo_ok = false;
>}
>#endif
>
>The same error someone reported some time ago with 2.6.2:
>
>http://www.mail-archive.com/lftp@uniyar.ac.ru/msg00888.html
>
>I also e-mailed the lftp-devel mailing-list.



This is a trick question, right?  I mean, you know how to search for a 
prototype in the system include directories don't you?  I'm assuming 
that you have a real question here but I can't figure out what it is.
Can you enlighten us/me?

BTW, the answer to Joe's question that you reference above is "No, 
setupterm() is not supposed to be part of libc (libcygwin.a).





Larry Hall                              lhall@rfk.com
RFK Partners, Inc.                      http://www.rfk.com
838 Washington Street                   (508) 893-9779 - RFK Office
Holliston, MA 01746                     (508) 893-9889 - FAX


--
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/

LFTP: Cygwin and setupterm

[Frédéric L. W. Meunier]

Anybody know what's wrong ? I tried to compile LFTP 2.6.3 with
ncurses 5.2-8 and got the following:

/cygdrive/g/Linux/lftp/src/lftp_tinfo.cc: In function `void init_terminfo()':
/cygdrive/g/Linux/lftp/src/lftp_tinfo.cc:50: implicit declaration of function `int setupterm(...)'

There's the following in lftp_tinfo.cc:

#if defined(HAVE_TIGETSTR)
static bool terminfo_ok = true;
static void init_terminfo()
{
   static bool initted = false;
   if(initted) return;
   initted = true;

   int errret=0;
   if(setupterm(NULL, 1, &errret) == ERR)
      terminfo_ok = false;
}
#endif

The same error someone reported some time ago with 2.6.2:

http://www.mail-archive.com/lftp@uniyar.ac.ru/msg00888.html

I also e-mailed the lftp-devel mailing-list.

-- 
0@pervalidus.{net, {dyndns.}org}


--
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/