From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 60455 invoked by alias); 7 Mar 2019 06:07:01 -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 60438 invoked by uid 89); 7 Mar 2019 06:07:01 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 spammy=O, appdata, o X-HELO: smtp-out-no.shaw.ca Received: from smtp-out-no.shaw.ca (HELO smtp-out-no.shaw.ca) (64.59.134.9) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 07 Mar 2019 06:06:59 +0000 Received: from [192.168.1.114] ([24.64.172.44]) by shaw.ca with ESMTP id 1mBFhoIYOdhgh1mBGhbY3l; Wed, 06 Mar 2019 23:06:58 -0700 Reply-To: Brian.Inglis@SystematicSw.ab.ca Subject: Re: Annoying error messages from setup To: cygwin@cygwin.com References: <2e2397a79c774d805d7a52dd2c5c3fb5@perezterron.net> <07ab08b1-b0cf-0df0-8dbc-0f1ad9f500ef@maxrnd.com> From: Brian Inglis Openpgp: preference=signencrypt Message-ID: <89054ee2-a5f6-e361-3b7d-a91ca035898e@SystematicSw.ab.ca> Date: Thu, 07 Mar 2019 06:07:00 -0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.5.2 MIME-Version: 1.0 In-Reply-To: <07ab08b1-b0cf-0df0-8dbc-0f1ad9f500ef@maxrnd.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-IsSubscribed: yes X-SW-Source: 2019-03/txt/msg00133.txt.bz2 On 2019-03-06 17:57, Mark Geisert wrote: > Enrique Perez-Terron wrote: >> For some time (several months), the setup program always finishes with the >> following message: >>> Package: _/cygwin-doc >>>     cygwin-doc.sh exit code 3 >>> Package: z/Perpetual >>>     zp_texlive_finish.dash exit code 20 >> Looking into setup.log.full, I find: >>> 2019/03/06 22:39:56 running: C:\cygwin\bin\bash.exe --norc --noprofile >>> "/etc/postinstall/cygwin-doc.sh" >>> mkshortcut: Saving "/cygdrive/c/ProgramData/Microsoft/Windows/Start >>> Menu/Programs/C:/cygwin/User Guide (PDF).lnk" failed; does the target >>> directory exist? >>> mkshortcut: Saving "/cygdrive/c/ProgramData/Microsoft/Windows/Start >>> Menu/Programs/C:/cygwin/User Guide (HTML).lnk" failed; does the target >>> directory exist? >>> mkshortcut: Saving "/cygdrive/c/ProgramData/Microsoft/Windows/Start >>> Menu/Programs/C:/cygwin/API (PDF).lnk" failed; does the target directory exist? >>> mkshortcut: Saving "/cygdrive/c/ProgramData/Microsoft/Windows/Start >>> Menu/Programs/C:/cygwin/API (HTML).lnk" failed; does the target directory exist? >>> mkshortcut: Saving "/cygdrive/c/ProgramData/Microsoft/Windows/Start >>> Menu/Programs/C:/cygwin/Home Page.lnk" failed; does the target directory exist? >>> mkshortcut: Saving "/cygdrive/c/ProgramData/Microsoft/Windows/Start >>> Menu/Programs/C:/cygwin/FAQ.lnk" failed; does the target directory exist? >>> 2019/03/06 22:39:57 abnormal exit: exit code=3 >> Where do the "/C:" parts in the middle of the link names come from? >> Investigating, I find that mkshortcut is being called like this: >>> /usr/bin/mkshortcut -A -P -n "Cygwin/User Guide (PDF)" -d "Cygwin User Guide >>> PDF" -- /usr/share/doc/cygwin-doc/cygwin-ug-net.pdf >>> /usr/bin/mkshortcut -A -P -n "Cygwin/User Guide (HTML)" -d "Cygwin User Guide >>> HTML" -- /usr/share/doc/cygwin-doc/html/cygwin-ug-net/index.html >>> /usr/bin/mkshortcut -A -P -n "Cygwin/API (PDF)" -d "Cygwin API Reference PDF" >>> -- /usr/share/doc/cygwin-doc/cygwin-api.pdf >>> /usr/bin/mkshortcut -A -P -n "Cygwin/API (HTML)" -d "Cygwin API Reference >>> HTML" -- /usr/share/doc/cygwin-doc/html/cygwin-api/index.html >>> /usr/bin/mkshortcut -A -P -n "Cygwin/Home Page" -d "Cygwin Home Page Link" -a >>> https://cygwin.com/index.html -- /usr/bin/cygstart >>> /usr/bin/mkshortcut -A -P -n "Cygwin/FAQ" -d "Cygwin Frequently Asked >>> Questions Link" -a https://cygwin.com/faq.html -- /usr/bin/cygstart >> There appears to be a bug in mkshortcut. >> Could this be somehow related to my enabling native symbolic links? >> (Not sure if this error began before I did that.) >> I don't know where to find the source for mkshortcut, and not sure if >> somebody else knows this program and can look into it. Should I report this >> somewhere? > Consider it reported :-O.  'cygcheck -p mkshortcut' shows mkshortcut is part of > the cygutils package.  I'm the maintainer.  You aren't using zsh as your shell, > are you?  I ask because zsh apparently has its own mkshortcut.  Let me > experiment a little bit and try to reproduce your first issue. > Your second issue is something totally separate and I can't help with it. The intent of the mkshortcut args -A --allusers from the $CYGWINFORALL setup env var switches -P --smprograms from using $APPDATA to using $ALLUSERSPROFILE as the prefix for -P .../Microsoft/Windows/Start Menu/Programs/ and -n Cygwin/... creates or uses the relative Cygwin subfolder to store the shortcuts. Could the existence of a C:/Cygwin/ root be confusing mkshortcut into using an absolute Windows path instead of a path relative to .../Start Menu/Programs/? -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada This email may be disturbing to some readers as it contains too much technical detail. Reader discretion is advised. -- 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