How to investigate a bug in /bin/mkshortcut.exe ?

Regid Ichira regid23@yahoo.com
Mon Oct 24 22:26:00 GMT 2011


On 24 October 2011 08:38:07 +0100, Andy Koppe wrote:

> On 23 October 2011 23:14, Regid Ichira wrote:
> > Â/etc/postinstall/mintty.sh's exit code is 127.
> >
> > Â Â$ cat /etc/postinstall/mintty.sh
> > Â ÂPROGS=$(/bin/cygpath -P $CYGWINFORALL)
> > Â Â/bin/mkdir -p "$PROGS/Cygwin" &&
> > Â Âcd "$PROGS/Cygwin" &&
> > Â Â/bin/mkshortcut -n mintty /bin/mintty -a - -d "Cygwin Terminal"
> >
> > By running those commands manually, I think the problem is the last,
> > /bin/mkshortcut, line. ÂHow can I investigate it more?
> >
> > Â Â$ cygcheck -f /bin/mkshortcut.exe
> > Â Âcygutils-1.4.6-1
> >
> > Â Â$ file /bin/mkshortcut.exe
> > Â Â/bin/mkshortcut.exe: PE32 executable (console) Intel 80386 (stripped to external PDB), for MS Windows
> 
> Try cygcheck without the -f to check that the DLLs that mkshortcut
> depends on are present.
> 
> cygcheck /bin/mkshortcut.exe
> 

  cygwin1.dll, cyggcc_s-1.dll and cygopt-0.dll are installed and up to date.
Would there be an explicit no permission message if the windows/system32/*.dll
user and group are not accessible by the uid owner of the process?


--
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



More information about the Cygwin mailing list