Re: [PATCH] Return argv0-symlink.exp early if gdb can't load symlink

[Yao Qi <yao@codesourcery.com>]

On 04/02/2014 04:43 PM, Yao Qi wrote:
> We run argv0-symlink.exp on mingw32 host, and see the following error
> in gdb.log
> 
> (gdb) file argv0-symlink-filelink^M
> "argv0-symlink-filelink": not in executable format: File format not recognized
> (gdb) ERROR: Couldn't load argv0-symlink-filelink into arm-none-eabi-gdb.
> 
> the rest of the test don't have to run.

Forget to mention that we run mingw32 toolchain test in cygwin, so
symbol link can be created (via command ln) successfully, but it is not
a real symlink, AFAIK, so this guard in argv0-symlink.exp below doesn't
return,

set status [remote_exec host "ln -sf . [standard_output_file $dirlink]"]
if {[lindex $status 0] != 0} {
    unsupported "$test (host does not support symbolic links)"
    return 0
}

Looks native windows symlinks are created on some versions of windows
with some features turned on, so we can't skip this test by checking
triplet of host.
http://cygwin.com/cygwin-ug-net/using.html#pathnames-symlinks

-- 
Yao (齐尧)