From: Robert Mark <robertmarkbram.lists@gmail.com>
To: cygwin@cygwin.com
Subject: Re: (core dumped) mkshortcut
Date: Mon, 10 Sep 2012 11:59:00 -0000 [thread overview]
Message-ID: <CAAcBW0xJ0gA7tgEWUsFOahPtFPWoOxHPPE1DBKjxoNWf0=3SHA@mail.gmail.com> (raw)
In-Reply-To: <CA+sc5mmKdBotzCPJTu4-QTpMtKUo4aMZoGPQQLEhOJ7vwEY+9Q@mail.gmail.com>
Hi Earnie,
>> As per a previous message
>> (http://cygwin.com/ml/cygwin/2012-05/msg00215.html) I am still finding
>> that mkshortcut causes core dumps (Windows 7, 64 bit). I have tried a
>> few different options: -P or -D still cause dumps. I have checked
>> permissions and they are all ok. Some folders do cause the error, some
>> don't.
>>
>> mkshortcut -n "I for cygwin bin" /D/cyghome/bin
>> /home/RobertMarkBram/bin/createWindowsShortcut.sh: line 160: 8128
>> Aborted (core dumped) mkshortcut -n "$shortcutName"
>> "$target"
>
> I'm going to guess but have no fact to back it that the reason is due
> to the fact you're executing in a 32bit environment and the shortcut
> the tool makes needs a 64bit enviroment. This may only be resolved by
> a 64bit version of Cygwin.
I did say I was running 64bit Win 7, so what exactly do you mean?
Cygwin.com says "The Cygwin DLL currently works with all recent,
commercially released x86 32 bit and 64 bit versions of Windows".
>> I am using an alternative as suggested:
>> http://cygwin.com/ml/cygwin/2012-05/msg00232.html
>>
>> It works OK, but isn't nearly as useful as mkshortcut: lnk files
>> handle rather differently than url files.
>
> You can still automate it. You just have to create a text file
> instead of a binary one.
I will try that - thanks.
Rob
:)
--
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:[~2012-09-10 11:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-09 4:43 Robert Mark
2012-09-09 17:34 ` Earnie Boyd
2012-09-10 11:59 ` Robert Mark [this message]
2012-09-10 13:00 ` Earnie Boyd
2012-09-10 19:20 ` Denis Excoffier
2012-09-11 5:58 ` Earnie Boyd
2012-09-11 8:00 ` Pawel Jasinski
2012-09-11 8:25 ` Pawel Jasinski
2012-09-11 12:18 ` marco atzeri
2012-09-12 12:21 ` Robert Mark
2012-09-12 13:33 ` Andrey Repin
2012-09-12 21:33 ` Andrey Repin
2012-09-12 13:02 ` Peter Rosin
2012-09-12 18:58 ` Charles Wilson
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='CAAcBW0xJ0gA7tgEWUsFOahPtFPWoOxHPPE1DBKjxoNWf0=3SHA@mail.gmail.com' \
--to=robertmarkbram.lists@gmail.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).