From: "Edvardsen Kåre" <kare.edvardsen@uit.no>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: What updates done after October 3 may affect gfortran built binaries?
Date: Wed, 09 Nov 2011 12:15:00 -0000 [thread overview]
Message-ID: <1320840871.13045.51.camel@kare-desktop> (raw)
This is again related to the failure of execution of a gfortran built
binary ("cannot execute binary", see thread
http://cygwin.com/ml/cygwin/2011-11/msg00034.html )
In short, the main problem is that I can't build a successful binary
from the FLEXPART fortran code (just google "FLEXPART nilu" if you are
curious of what FLEXPART is) on a cygwin installation I did just over a
week ago, but it builds and run without problem on an installation from
October 3. I get no differences in warnings from the bad build compared
to the good one, so I really don't know what to look for.
So far I have come to the conclusion that this must be related to one or
several changes in the cygwin distribution done after October 3. Through
try and failure testing I found that this is not affected by
gfortran/gcc as both gcc 4.3.4 and gcc 4.5.3 works. The latter hangs on
'$EGREP' calls in the 'grib_api' (required library) configure script,
but the workaround of changing to 'egrep' works fine.
I have posted the output from strace, objdump and cygcheck for some of
you to look at in the former thread, but it seem like this is far from a
straight forward problem.
I can see from the [ANNOUNCEMENT] posts that a few things in this cygwin
distro have been updated since October 3 and I kindly ask if someone
have an idea of what updates since then may cause a badly gfortran built
binary if it has nothing to do with gcc alone?
I will now start going through the updates and change back to versions
yielding October 3 if possible. I think this is important since cygwin
will give the opportunity to run and develop FLEXPART on Windows
machines the way linux-users are used to. In addition, I also see a
potential problem of other fortran software that people want to run
under cygwin.
Regards,
Kåre
next reply other threads:[~2011-11-09 12:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-09 12:15 Edvardsen Kåre [this message]
2011-11-09 13:07 ` Marco Atzeri
2011-11-15 15:54 ` [SOLVED] " Dave Korn
2011-11-15 16:21 ` Ryan Johnson
2011-11-15 22:55 ` Dave Korn
2011-11-09 13:32 Edvardsen Kåre
2011-11-10 5:24 ` Dave Korn
2011-11-10 9:49 Edvardsen Kåre
2011-11-10 9:55 Edvardsen Kåre
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=1320840871.13045.51.camel@kare-desktop \
--to=kare.edvardsen@uit.no \
--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).