This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

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


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

Andy

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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]