This is the mail archive of the
mailing list for the Cygwin project.
Re: cyggfortran-3.dll broken ?
- From: Dave Korn <dave dot korn dot cygwin at gmail dot com>
- To: cygwin at cygwin dot com
- Date: Tue, 29 Mar 2011 14:35:55 +0100
- Subject: Re: cyggfortran-3.dll broken ?
- References: <4D9134DD.email@example.com>
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.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple