> -----Original Message-----
> From: cygwin-owner On Behalf Of Thorsten Kampe
> Sent: 19 July 2004 12:48
> Hi,
>
> I often get the message from configure scripts for applications that
> are curses-based that no ncurses could be found (although it actually
> is installed[1] and many applications happily use it)
>
> What's going wrong
Dunno, but I have some generic autoconf advice: Take a look at the
config.log file generated by configure. It'll contain output from the
attempt to test curses that should show what the test tried to do and why it
failed; then you'll have a clearer idea what's up.
> and how can I point the configure script to my
> "ncurses" dlls? Any environment variable or something like that?
...always assuming that is the problem, of course. And the answer is, we'll
have to look at config.log to see why the configure script isn't already
finding your ncurses install before we can figure out how to point it at the
relevant files...
cheers,
DaveK
--
Can't think of a witty .sigline today....
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
