From: Mark Geisert <mark@maxrnd.com>
To: cygwin@cygwin.com
Subject: Re: Annoying error messages from setup
Date: Thu, 07 Mar 2019 00:57:00 -0000 [thread overview]
Message-ID: <07ab08b1-b0cf-0df0-8dbc-0f1ad9f500ef@maxrnd.com> (raw)
In-Reply-To: <2e2397a79c774d805d7a52dd2c5c3fb5@perezterron.net>
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.
..mark
--
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
next prev parent reply other threads:[~2019-03-07 0:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-07 0:02 Enrique Perez-Terron
2019-03-07 0:57 ` Mark Geisert [this message]
2019-03-07 6:03 ` Mark Geisert
2019-03-07 6:11 ` Brian Inglis
2019-03-07 6:07 ` Brian Inglis
2019-03-08 8:52 ` Mark Geisert
2019-03-07 12:47 ` Ken Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=07ab08b1-b0cf-0df0-8dbc-0f1ad9f500ef@maxrnd.com \
--to=mark@maxrnd.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).