[PATCH] Skip gcore-buffer-overflow.exp on windows

[Yao Qi]

On 11/16/2012 11:56 PM, Eli Zaretskii wrote:
> This is still less than 256 characters, so I don't understand why it
> fails.  And you can make it even less if you use relative file names.

My experiments show that the max length of file name is 241.

$  i686-pc-linux-gnu-gcc.exe gcore-buffer-overflow.c   -g  -lm   -o 
gcore-buffer-overflow111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111222222222222222222222222222223567

We'll get the error when file name length is 242.

$  i686-pc-linux-gnu-gcc.exe gcore-buffer-overflow.c   -g  -lm   -o 
gcore-buffer-overflow1111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111112222222222222222222222222222235678
c:/cygwin/home/yqi/test-i686-mingw32/test-build5-lucid-cs/ia32-2012.09/bin/../lib/gcc/i686-pc-linux-gnu/4.7.2/../../../../i686-pc-linux-gnu/bin/ld.exe: 
cannot open output file 
gcore-buffer-overflow1111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111112222222222222222222222222222235678: 
No such file or directory

and I checked that 'fopen' can't open the file whose length exceeds 241. 
  However, I can 'cp' or 'mv' file to the file with long file name (242 
~ 256)..  Any ideas?

-- 
Yao (齐尧)