On Fri, Apr 15, 2011 at 3:32 PM, Fergus wrote:
> Using cygwin 1.7 and gcc 3.4.4 I have a line in a script
>
> gcc -o myexec -o3 ./my.a -lreadline -lncurses -lm
>
> which has worked since the Dawn of Time. Just now I had to rebuild myexec
> and got an error message
>
> /usr/lib/gcc/i686-pc-cygwin/3.4.4/../../../../i686-pc-cygwin/bin/ld: cannot
> find -lncurses
> collect2: ld returned 1 exit status
>
> Strange because I have
>
> setup.exe -P {variouspackages},ncurses,{morepackages}
>
> as my one-line setup command (also with a long history of nofail working).
> But on inspection I see files and folders
>
> /usr/include/ncursesw NOT /usr/include/ncurses
> /usr/lib/ncursesw* NOT /usr/include/ncurses*
>
> all dated Feb 15. Did I miss some massive re-configuration and re-naming
> then?
>
> Rewriting the gcc line with -lncursesw not -lncurses works.
>
> However ... I'd quite like to keep this line for the simple reason that it
> works in Linux as well as (up to now) Cygwin. I could write a branch but I'd
> prefer to write a link something like
>
> ln -s ncursesw ncurses
>
> under /usr/include/ or something similar but presumably more complicated
> under /usr/lib/.
>
> Have I identified the cause of the breakage (some kind of supersession on or
> about Feb 15)? Have others tripped up? Is there a good cure?
http://cygwin.com/packages/libncurses-devel/libncurses-devel-5.7-18
>
> Thank you.
>
> Fergus
>
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
