public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Larry Hall (RFK Partners, Inc)" <lhall@rfk.com>
To: "Sukhwinder Singh" <ssruprai@hotmail.com>, <cygwin@cygwin.com>
Subject: Re: Manual setup of cygwin  - solved but ncurses Error unable to open terminal: cygwin
Date: Mon, 06 May 2002 20:58:00 -0000	[thread overview]
Message-ID: <4.3.1.2.20020506234625.02632ee8@pop.ma.ultranet.com> (raw)
In-Reply-To: <OE14fOImd1UtYj7XGeF000082a5@hotmail.com>

At 11:25 AM 5/7/2002, Sukhwinder Singh wrote:
>Hello Sir,
>
>Thank you very much for your help. I was able to solve this problem of
>setting up cygwin dir as root dir. I chose to do it myself because setup.exe
>wasn't downloading anything.


Hm, did you report the specifics of this behavior to the list?  That's the 
recommended approach.  Of course, you're always free to pursue your own 
fancy in terms of a resolution.  But this list usually isn't too concerned
with problems generated by home-brewed installations.  That's why using and
improving setup is highly encouraged.


>After I tried I was able to do something like this to enable scripts to find
>/bin/sh and /usr/bin etc.
>
>BASH-2.05a$ mount /cygwin/ /
>BASH-2.05a$
>
>I am able to do cd /bin and cd /usr/bin etc.
>
>I was even able to compile zlib library using cygwin and mingW.
>
>But now I am missing something as libncurses demo programs didn't run
>because it was unable to start terminal etc.
>termcap is in directory /etc.
>
>Ncurses dlls etc are in path.
>
>When I run the demo programs in /usr/bin/ncurses-test-dll/ following error
>is displayed.
>
>BASH-2.05a$ ./blue
>Error opening terminal: cygwin.
>BASH-2.05a$
>
>Is there anything which I forgot to download? What is the problem here?


I would've said you don't have /etc/termcap but you obviously do.  Perhaps 
it's wrong.  In terms of the ncurses tests, are you sure you don't need a 
terminfo entry and/or that the TERMINFO and TERMCAP environment variables are
set correctly?  These are the only generic configuration issues I can think of 
in this regard.  Of course, there are a bunch of issues that can come as a 
result of a not-properly-installed environment from the use of faulty tools.
Since I don't know (and I'm not sure that I care to know) the tools you used
to create your installation, I can't rule out that your installation isn't
corrupt.  So overall, I'm not that interested in trying to debug this problem
with you.  Perhaps you want to try setup again and tell the list the specifics 
of the problems you're having with it?



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/

      reply	other threads:[~2002-05-07  3:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-06 20:25 Sukhwinder Singh
2002-05-06 20:58 ` Larry Hall (RFK Partners, Inc) [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=4.3.1.2.20020506234625.02632ee8@pop.ma.ultranet.com \
    --to=lhall@rfk.com \
    --cc=cygwin@cygwin.com \
    --cc=ssruprai@hotmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).