Native symlinks and setup.exe

Gene Pavlovsky
Sun Oct 2 23:35:00 GMT 2016


That's a great pointer. I've just investigated using the `flex`
package as an example.
Untarring flex-2.6.1-1.tar.xz, usr/bin/flex++ is extracted as a Cygwin
symlink to usr/bin/flex.exe.
If I create a native symlink to flex.exe, tar it all up to a new tar
archive, then extract it somewhere else, the native symlink is
extracted as native, as expected.

So, when installing, the type of symlinks doesn't honor the CYGWIN
option since they are just unpacked by tar as is.

The question I'm proposing now - should `tar` be modified to honor the
CYGWIN option and automatically convert symlinks when extracting, if


On 2 October 2016 at 14:00, Thorsten Kampe <> wrote:
> * Gene Pavlovsky (Sat, 1 Oct 2016 18:52:47 +0300)
>> I'm installing Cygwin 64-bit on a fresh Win 7 x64 installation.
>> Before running setup.exe I've set the system env var CYGWIN=winsymlinks:native
>> After that I ran setup-x86_64.exe and installed cygwin64.
>> The symlinks to .exe files in bin, created by setup, are not native
>> symlinks, they are cygwin symlinks. Apparently, setup doesn't honor
>> the winsymlinks:native CYGWIN option. Is that intended (why?) or a
>> bug?
> Setup does not create symlinks. That's either done by the postinstall
> scripts or the contents of the package are simply unpacked to the
> folder. So the answer to your question is: the symlinks are not
> created but copied, that's why.
> Thorsten
> --
> Problem reports:
> FAQ:         
> Documentation:
> Unsubscribe info:

Problem reports:
Unsubscribe info:

More information about the Cygwin mailing list