windows 64bit build failures, not always, randomly failing

[Kelly O'Hair]

Just an FYI...

I seem to be getting the Windows 2003 X64 failures running /usr/bin/grep:

...
/usr/bin/grep -e '\.class$' /cygdrive/c/jprt/T/P1/203843.jprtadm/s/build/windows-x86_64-normal-server-release/jdk/lib/_the.jars.contents >
 /cygdrive/c/jprt/T/P1/203843.jprtadm/s/build/windows-x86_64-normal-server-release/jdk/lib/_the.rt.jar.contents.tmp
/usr/bin/mkdir -p /cygdrive/c/jprt/T/P1/203843.jprtadm/s/build/windows-x86_64-normal-server-release/jdk/lib
/usr/bin/rm -f /cygdrive/c/jprt/T/P1/203843.jprtadm/s/build/windows-x86_64-normal-server-release/jdk/lib/_the.resources.jar.contents
 /cygdrive/c/jprt/T/P1/203843.jprtadm/s/build/windows-x86_64-normal-server-release/jdk/lib/_the.resources.jar.contents.tmp
make[3]: *** [/cygdrive/c/jprt/T/P1/203843.jprtadm/s/build/windows-x86_64-normal-server-release/jdk/lib/_the.rt.jar.contents] Error 1
make[3]: *** Waiting for unfinished jobs....

The grep:

/usr/bin/grep -e '\.class$' _the.jars.contents > _the.rt.jar.contents.tmp

is failing with an Error 1.

Found this reference:
     http://cygwin.com/ml/cygwin/2009-05/msg00036.html

Yipes... grep can fail if the grep console output is more than 64K???  :^(

I assume that by doing a parallel build we are pushing the Windows virtual memory hard, and we could
be experiencing all kinds of 'cannot allocate' situations?????

-kto