From: marco atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: clisp crashes on startup
Date: Sat, 07 Jul 2012 17:45:00 -0000 [thread overview]
Message-ID: <4FF8759A.10400@gmail.com> (raw)
In-Reply-To: <CAHiT=DF+JfGcMVJ5x05cu1c7tZniRUfeTNNnBf4tzrHZq99+jA@mail.gmail.com>
On 7/7/2012 6:19 PM, Reini Urban wrote:
> On Sat, Jul 7, 2012 at 8:41 AM, Daniel Colascione wrote:
>> On 7/7/12 6:04 AM, marco atzeri wrote:
>>> On 7/7/2012 12:45 AM, Daniel Colascione wrote:
>>>> $ clisp
>
> Looks like a missing dependency or wrong dll perm. I saw none in your cygcheck.
>
> Can you try
> $ ldd /usr/lib/clisp-2.48/base/lisp.exe
> and see of one dll is missing.
> And check if one of the dll's has no x perm set.
$ cygcheck /usr/lib/clisp-2.48/base/lisp.exe
should be better. ldd does not advise about missing dll's
>
> clisp.exe is just a driver, which exec's base/lisp.exe or full/lisp.exe
>
Regards
Marco
--
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-07-07 17:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-06 22:47 Daniel Colascione
2012-07-07 13:04 ` marco atzeri
2012-07-07 13:41 ` Daniel Colascione
2012-07-07 16:19 ` Reini Urban
2012-07-07 17:45 ` marco atzeri [this message]
2012-07-07 19:08 ` Daniel Colascione
2012-07-09 21:01 ` Reini Urban
2012-07-09 21:27 ` Daniel Colascione
2012-07-10 4:59 ` Daniel Colascione
2012-07-10 8:14 ` Corinna Vinschen
2012-07-10 15:42 ` Daniel Colascione
2012-07-13 3:48 ` Daniel Colascione
2012-07-13 7:41 ` Corinna Vinschen
2012-07-13 12:53 ` Reini Urban
2012-07-13 14:27 ` Corinna Vinschen
2012-07-13 16:30 ` Reini Urban
2012-07-13 17:46 ` Daniel Colascione
2012-07-07 17:05 ` Andrey Repin
2012-07-07 19:04 ` Daniel Colascione
2012-07-08 23:20 ` Andrey Repin
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=4FF8759A.10400@gmail.com \
--to=marco.atzeri@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).