On Tue, Jul 05, 2005 at 07:25:04PM +0000, Eric Blake wrote: >It is annoying that cygcheck exits with status 0, even if it could not find a >file: > >$ cygcheck /bin/lilypond.exe >C:/cygwin/bin/lilypond.exe > C:/cygwin/bin\cygwin1.dll > C:\WINNT\system32\ADVAPI32.DLL > C:\WINNT\system32\NTDLL.DLL > C:\WINNT\system32\KERNEL32.DLL > C:\WINNT\system32\RPCRT4.DLL > C:/cygwin/bin\cygguile-12.dll > C:/cygwin/bin\cygcrypt-0.dll > C:/cygwin/bin\cygguile-ltdl-1.dll > C:/cygwin/bin\cygintl-3.dll > C:/cygwin/bin\cygiconv-2.dll >Error: could not find cygkpathsea-4.dll >$ echo $? >0 >$ cygcheck none >Error: could not find none >$ echo $? >0 > >This makes exit status worthless when trying to use cygcheck to verify if >an existing file has any broken dependencies (a la the bash upgrade >scenarios being discussed on cygwin-apps). I tried to prepare a patch, >but returning EXIT_FAILURE from main() still produced a 0 exit status, >so it might be that the magic that makes cygcheck know about >cygwin1.dll while still being a Windows app needs fixing, too.
This should be fixed in the current snapshot. cgf -- 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/
