From: Dave Korn <dave.korn.cygwin@gmail.com>
To: cygwin@cygwin.com
Subject: Re: cyggfortran-3.dll broken ?
Date: Tue, 29 Mar 2011 13:46:00 -0000 [thread overview]
Message-ID: <4D91E03B.3010307@gmail.com> (raw)
In-Reply-To: <4D9134DD.5070700@byu.net>
On 29/03/2011 02:24, Daniel Jensen wrote:
> Since Dave Korn was wondering how many people this would be bothering,
> I'm just chiming in to say I was bitten by this too (since I both run
> cygwin setup less often than others and use octave less often than
> others, and since I'm not subscribed to the list, I'm late to the
> party). It was kind of baffling to have no output, error message, core
> dump, etc- just an immediate return
I'm sure there was an error code set in the $? shell variable, but we do
have a reporting issue there that bash doesn't always issue a message when a
process fails with an error status.
> regardless of what command line
> options I specified- and to have cygcheck say all was well with the
> library situation.
Yeh, this is a limitation of cygcheck; it only checks if the named DLLs are
present, not if they have all the necessary imports that the executable
actually requires. It /could/ be added to cygcheck but would need a good deal
of extra code to be written by someone.
cheers,
DaveK
--
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:[~2011-03-29 13:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-29 1:31 Daniel Jensen
2011-03-29 13:46 ` Dave Korn [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-03-23 15:07 marco atzeri
2011-03-23 16:12 ` Dave Korn
2011-03-23 16:19 ` Dave Korn
2011-03-23 16:19 ` marco atzeri
2011-03-23 16:35 ` Dave Korn
2011-03-23 16:37 ` marco atzeri
2011-03-23 17:29 ` Don Ward
2011-03-23 18:44 ` marco atzeri
2011-03-23 16:38 ` Corinna Vinschen
2011-03-23 16:58 ` Dave Korn
2011-03-23 16:36 ` Charles Wilson
2011-03-23 17:15 ` Dave Korn
2011-03-23 17:35 ` Charles Wilson
2011-03-23 17:51 ` Dave Korn
2011-03-23 19:41 ` Charles Wilson
2011-03-23 19:45 ` Dave Korn
2011-03-23 19:50 ` marco atzeri
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=4D91E03B.3010307@gmail.com \
--to=dave.korn.cygwin@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).