From: "Edvardsen Kåre" <kare.edvardsen@uit.no>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: Problem with execution of binary file
Date: Tue, 08 Nov 2011 11:22:00 -0000 [thread overview]
Message-ID: <1320751280.5480.279.camel@kare-desktop> (raw)
> Mark Geisert (that's me) wrote:
> > I haven't yet diff'd the two cygchecks
> > you sent but maybe that'll lead somewhere.
>
> I've now done that. The 'good' cygcheck shows many more packages installed than
> the 'bad' cygcheck. But the only package version differences I found were for
> bzr, find and mercurial; the 'good' cygcheck paradoxically shows earlier
> versions for those three packages. Hard to see how those package differences
> could matter though.
>
> About the only thing I can think of, and it's a crazy idea, is that the 'good'
> environment, with more packages installed, is somehow supplying something that's
> emulated badly in the 'bad' environment. Figuring out if that's the case would
> involve building your executable with every possible "verbose" switch turned on
> so you can identify exactly where every item going into the executable is coming
> from. Repeated in both 'good' and 'bad' environments.
>
> Or, you could take heart that you've got a good build you can work with now and
> just run with that. Maybe somebody else has another approach to try.
> HTH,
>
> ..mark
>
Yes, the 'good' installation was done Oct. 3 with many more packages
than the bad one. Just a week ago I wanted to install cygwin and run my
software on other machines, and then I ran into this problem. It's not a
paradox that the good installation has earlier package versions since it
was installed a month earlier than the bad one :)
So, my problem is now to isolate what has changed since then, which is
affecting the build of my fortran binary.
There is one thing I remember that is different now when I install a
required library (grib-api, see post
http://cygwin.com/ml/cygwin/2011-10/msg00037.html)
I did not experience this hang back one month ago, but I've upgraded gcc
since then, and I wonder if the grib_api, and then my software, is
affected by this.
I will try to rebuild everything with gcc 4.3.4 too se if it helps, and
report the result to the list.
Cheers
next reply other threads:[~2011-11-08 11:22 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-08 11:22 Edvardsen Kåre [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-11-07 9:55 Edvardsen Kåre
2011-11-07 19:26 ` Mark Geisert
2011-11-08 10:02 ` Mark Geisert
2011-11-08 10:08 ` Mark Geisert
[not found] <1320325271.5480.163.camel@kare-desktop>
2011-11-03 13:19 ` Edvardsen Kåre
2011-11-03 12:21 Edvardsen Kåre
2011-11-03 12:53 ` Corinna Vinschen
2011-11-03 13:22 ` Eliot Moss
2011-11-03 14:11 ` Edvardsen Kåre
2011-11-03 19:54 ` Mark Geisert
2011-11-03 21:57 ` Eliot Moss
2011-11-04 1:54 ` Eliot Moss
2011-11-04 8:51 ` Edvardsen Kåre
2011-11-04 10:50 ` Eliot Moss
2011-11-04 12:34 ` Edvardsen Kåre
2011-11-04 17:56 ` Mark Geisert
2011-11-04 18:00 ` Eliot Moss
2011-11-04 18:21 ` Mark Geisert
2011-11-05 9:52 ` David Sastre
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=1320751280.5480.279.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).