Re: bug #2813561 with cygwin symlinks

[Reini U. <ru...@x-...>]

2010/3/29 Arseny Slobodyuk <am...@ic...>:
> Hello Reini,
>
> Tuesday, March 30, 2010, 12:43:13 AM, you wrote:
>
>> Symlinks are used by -K full to resolve duplicate files.
>> How the symlinks are interpretated is solely a cygwin runtime issue.

> This functionality, in fact used only by mingw build
> when (freshly built) clisp needs to read some symlinked files.
> When building with MSVC (I didn't tried it for a long time and believe
> it's quite a challenge for now) it isn't used because the build occurs
> in source dir. But I believe, MSVC build or, say, build with
> `different compiler' should use the same machinery as mingw so ability
> of reading cygwin symlinks is important (unless Sam agrees to change
> `ln -s' to `cp' in such cases).
>
>> CYGWIN=winsymlinks is for the old behaviour, using old-style windows .lnk files
>> Since cygwin 1.7 the default is using a shorter magic symlink file.

> Thanks for explaining. So mingw build is in trouble.

I see. So a mingw build in a cygwin terminal (aka MSYS) requires a
export CYGWIN=winsymlinks

And the installation requires a cp.
-- 
Reini Urban