Library missing, but do not know which one :-(

2011-02-03 Thread Muzzy
Hello, when I start bc command in cygwin following error occurs: /usr/bin/bc.exe: error while loading shared libraries: ?: cannot open shared object file: No such file or directory What can I do in this case ? I installed only bash, bc and xterm packages. cygcheck -s -v -r

Re: Library missing, but do not know which one :-(

2011-02-03 Thread Larry Hall (Cygwin)
On 2/3/2011 11:35 AM, Muzzy wrote: Hello, when I start bc command in cygwin following error occurs: /usr/bin/bc.exe: error while loading shared libraries: ?: cannot open shared object file: No such file or directory What can I do in this case ? I installed only bash, bc and xterm packages.

Re: Library missing, but do not know which one :-( [attn bc maintainer]

2011-02-03 Thread Eric Blake
On 02/03/2011 12:50 PM, Larry Hall (Cygwin) wrote: 'cygcheck bc' should tell you which DLL is missing. Looking at the list, there's not allot that's Cygwin there: C:\bin\cygreadline6.dll C:\bin\cygncurses-9.dll C:\bin\cyggcc_s-1.dll And of course cygwin1.dll. Aircrack has

Re: Library missing, but do not know which one :-( [attn bc maintainer]

2011-02-03 Thread Eric Blake
On 02/03/2011 01:04 PM, Eric Blake wrote: C:\bin\cygreadline6.dll C:\bin\cygncurses-9.dll C:\bin\cyggcc_s-1.dll Aha. Bash used to pull in libncurses9 by default, but now it pulls in libncursesw10. This is a setup.hint issue; bc was listing libncurses8 instead of

Re: Library missing, but do not know which one :-(

2011-02-03 Thread Muzzy
Looks to me, though, like you're missing the libncurses9 package. I'd try that. libncurses9 was the missing one :-) Thanks a lot ! -- View this message in context: http://old.nabble.com/Library-missing%2C-but-do-not-know-which-one-%3A-%28-tp30837080p30839158.html Sent from the Cygwin list

Re: Library missing, but do not know which one :-( [attn bc maintainer]

2011-02-03 Thread Christopher Faylor
On Thu, Feb 03, 2011 at 01:04:22PM -0700, Eric Blake wrote: I've updated the hint on cygwin's site, but the maintainer needs to fix it locally for the next time bc is updated In this particular case the maintainer has asked that changes not be made to his packages since he is capable of making