From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 115457 invoked by alias); 1 Oct 2016 21:32:29 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 115441 invoked by uid 89); 1 Oct 2016 21:32:27 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.4 required=5.0 tests=BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,RCVD_IN_SORBS_SPAM,SPF_PASS autolearn=no version=3.3.2 spammy=pavlovsky, Pavlovsky, H*i:sk:_8WJtxO, H*f:sk:CAPTiy3 X-HELO: mail-wm0-f47.google.com Received: from mail-wm0-f47.google.com (HELO mail-wm0-f47.google.com) (74.125.82.47) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sat, 01 Oct 2016 21:32:26 +0000 Received: by mail-wm0-f47.google.com with SMTP id f193so6451122wmg.0 for ; Sat, 01 Oct 2016 14:32:25 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:subject:to:references:from:message-id :disposition-notification-to:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=WjoCpMdaRJtXmGHdT6pPgflrQpJwC+slZKX+7BwlVYE=; b=ia7vjJHaf+RHyc9IFjZPfCaZDNVD85pXS9rk/GIaIIe90UFfmYrJqZOil0wAabjOiU XbyoI9AgU+IGvsKYYR2o9ZoRhPpxmg7pKNfvRJvxmjfCh1Dq0XHemph1r2Y8HhOq9Jdo EgjTtTgM0hdotq2Opsz4zzoNaPMs/0CIlshyCYsZ4hdozTwF/SjeSARNYIvB6Gq5H9Jv PyxRFcvfjCzVpbWSg3UPOkcFlTl8wYvSydMAlKfoJlCwG7WNSjljI+ZP4hPYgJk1Cqa2 eWXrpQiYS1dnGSwUElTi3HA3h2GCYulUz41S7xyWjZN+Lh6IKgkg3HZ9CVV+HA+Qh+nc xkgQ== X-Gm-Message-State: AA6/9Rml+z6+KgoUD7t+YDRDw8nPOhsRbMhPRwL0s6q2Rji1/IcQhJIpO8H4k4tnljGv0Q== X-Received: by 10.28.134.8 with SMTP id i8mr3064947wmd.59.1475357543963; Sat, 01 Oct 2016 14:32:23 -0700 (PDT) Received: from [192.168.88.32] (ip202.213-181-143.pegonet.sk. [213.181.143.202]) by smtp.gmail.com with ESMTPSA id y2sm26438878wji.42.2016.10.01.14.32.23 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 01 Oct 2016 14:32:23 -0700 (PDT) Subject: Re: Native symlinks and setup.exe To: cygwin@cygwin.com References: From: Vlado Message-ID: <6b81e0d4-f9ac-a997-54f7-4c30347b61f3@gmail.com> Date: Sat, 01 Oct 2016 21:56:00 -0000 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2016-10/txt/msg00008.txt.bz2 On 1.10.2016 17:52, Gene Pavlovsky wrote: > 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? Hi Gene, IMHO CYGWIN variable controls Cygwin behavior, but setup is native Windows app. What You are describing is expected behavior. Vlado. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple