Re: Problem with execution of binary file

["Edvardsen Kåre" <kare.edvardsen@uit.no>]

On fr., 2011-11-04 at 05:50 -0500, Eliot Moss wrote:
> On 11/4/2011 3:50 AM, Edvardsen Kåre wrote:
> >
> >> On 11/3/2011 4:56 PM, Eliot Moss wrote:
> >>          Ok, so here's one thing about bash: to get it to
> >>          run an *executable* (as opposed to a *script*),
> >>          you need to say "bash -c FLEXPART_GFORTRAN".
> >>          You might try strace on that. In addition to the
> >>          objdump suggestion.
> >>
> >> I have a moment to expand on this a little. The
> >> 80-byte read we saw was bash looking at the
> >> beginning of what it that was supposed to be a
> >> script (not a binary) and seeing if it really
> >> appeared to be a script. I did not look like a
> >> script, so bash gave up. (It checks whether the
> >> first line is all printable characters or white
> >> space.)
> >>
> >> Best -- Eliot Moss
> >>
> >
> > Hmm, wonder why bash would interpret it as a script. Anyway, I will get
> > back to you later with output from strace and objdump.
> 
> Because you did not specify -c ... EM

I'm still learning :)

Anyway, I've installed two versions of cygwin on the same machine - the
first was installed around Oct. 3 and the second one from a few days
ago. Compiling exactly the same software on both versions gives success
on the older installation and failure on the newer one. Could it be that
newer versions of some libs/compilers have bugs? Something different
between those two versions is for sure causing the problem.
Oviously, I'm using gfortran for building FLEXPART_GFORTRAN but I've
also installed from source the latest version of "jasper" and "grib_api"
libs (required by my FLEXPART software), and I'm not sure in detail what
is involved in building those libs.

Do you have any immediate idea of what could be the potential problem?

Cheers,
Kåre