latest cygcheck -c is expensive

Jason Tishler
Mon Sep 8 11:46:00 GMT 2003


On Sun, Sep 07, 2003 at 12:30:21AM -0400, Christopher Faylor wrote:
> On Sun, Sep 07, 2003 at 12:28:05AM -0400, Christopher Faylor wrote:
> >On Fri, Sep 05, 2003 at 08:42:49PM -0400, Jason Tishler wrote:
> >>On Fri, Sep 05, 2003 at 03:01:27PM -0400, Christopher Faylor wrote:
> >>> If the only concern is that cygcheck takes a long time, now, then,
> >>> like I said, that is something that can be rectified.
> >>
> >>Yes, the above is my real concern.
> >
> >I just hacked cygcheck to avoid calling gzip and use a mingw libz.a
> >(courtesy of Chuck Wilson) and it takes 26 seconds to complete on my
> >dual PIII 733MHZ WinXP system.  I have most packages installed.
> >
> >Is that still too slow?
> I should add that the previous version took 1 minute, 9 seconds.

Approximately 3 time faster is a significant improvement, but IMO,
anything more than a few seconds is still too "expensive."

What about an option to disable the sanity checking?  In this way,
Cygwin users do not need to learn new tricks, but powers user still get
the control they desire.

BTW, I tried to give cygcheck from the 2003-Sep-08 snapshot a ride.  The
ChangeLog and diff seem to indicate the required changes have been
completed.  Unfortunately, my timing showed no difference and objdump
showed no dependency on Mingw zlib:

    $ objdump -p cygcheck.exe | fgrep 'DLL Name:'
            DLL Name: msvcrt.dll
            DLL Name: msvcrt.dll
            DLL Name: ADVAPI32.DLL
            DLL Name: KERNEL32.dll

Is the above cockpit error on my part?


PGP/GPG Key: or key servers
Fingerprint: 7A73 1405 7F2B E669 C19D  8784 1AFD E4CC ECF4 8EF6

Unsubscribe info:
Problem reports:

More information about the Cygwin mailing list