public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Charles Wilson <cwilson@ece.gatech.edu>
To: Felix Natter <f.natter@ndh.net>
Cc: cygwin@cygwin.com
Subject: Re: broken ncurses-installation
Date: Wed, 02 May 2001 11:13:00 -0000	[thread overview]
Message-ID: <3AF04EE0.1970FC9C@ece.gatech.edu> (raw)
In-Reply-To: <8766fjpydh.fsf@mybaby.home.felix>

Felix, this is the second time you have explicitly listed your "command
line" -- but that "command line" did not have the required '-lcurses'
argument.  This is also the second time you have claimed, "oh yeah, I
"of course" had that option" after somebody pointed out that it was
missig.  Are you SURE you had the -lcurses?  (Or did you forget to type
the MOST IMPORTANT fraggin' part of the command in TWO separate email
messages, but "of course" NOT forget when typing it in their shell?  --
cut-n-paste from the command window is your friend...)

Also, the fact that '-lcurses' was not included in your email messages
means that we don't know *where* in your command line the 'lcurses'
argument appeared (you know it has to come *after* the object files that
require it, right?)

Finally, you *MAY* be running in to some hitherto unknown symlink
problem.  /usr/lib/libcurses.a/libcurses.dll.a are symlinks to
/usr/lib/libncurses.a/libncurses.dll.a.  Try using '-lncurses' instead
of '-lcurses'.

I'm sorry, but I can't reproduce your problem.  However, I don't think
there's anything wrong with your installation method; you are missing a
few packages but those absenses should not affect your test program's
build. 

Having a space in your homedir name is probably not a good idea.
Having a space in your login name is probably not a good idea.
Having TEMP=something with /cygdrive/ in it is not good.

> gcc -static -DNCURSES_STATIC -o test_curses.exe test_curses
> => undefined reference to endwin ...
> gcc -o test_curses.exe test_curses.c
> => undefined reference to _imp__endwin ...

The results of these two commands indicate that you DO have
/usr/include/curses.h.  However, let's check the basics: do the files
/usr/lib/libncurses.a and/or /usr/lib/libncurses.dll.a exist?  Do the
symlinks /usr/lib/libcurses.a and/or /usr/lib/libcurses.dll.a exist?

--Chuck


Felix Natter wrote:
> 
> egor duda <deo@logos-m.ru> writes:
> 
> > Hi!
> >
> > Tuesday, 01 May, 2001 Felix Natter f.natter@ndh.net wrote:
> >
> > FN> hi,
> >
> > FN> gcc -static -DNCURSES_STATIC -o test_curses.exe test_curses
> > =>> undefined reference to endwin ...
> this should be:
>         gcc -lcurses -static -DNCURSES_STATIC -o test_curses.exe test_curses
> > you want to add '-lcurses' to the command line, just like it's being
> > done on Linux.
> 
> Sorry, once again I forgot to mention this. Of course I added -lcurses to
> the line (I also tried to list the static library with the full path).
> 
> --
> Felix Natter
> 
> --
> Want to unsubscribe from this list?
> Check out: http://cygwin.com/ml/#unsubscribe-simple

--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2001-05-02 11:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-01  6:32 Felix Natter
2001-05-01  6:43 ` egor duda
2001-05-02  8:34   ` Felix Natter
2001-05-02 11:13     ` Charles Wilson [this message]
2001-05-03 11:06       ` Felix Natter
2001-05-01  7:45 ` Earnie Boyd

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=3AF04EE0.1970FC9C@ece.gatech.edu \
    --to=cwilson@ece.gatech.edu \
    --cc=cygwin@cygwin.com \
    --cc=f.natter@ndh.net \
    /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).