This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: g77 on cygwin64
- From: Achim Gratz <Stromeko at nexgo dot de>
- To: cygwin at cygwin dot com
- Date: Wed, 12 Feb 2014 20:38:13 +0100
- Subject: Re: g77 on cygwin64
- Authentication-results: sourceware.org; auth=none
- References: <52FAF082 dot 6020805 at appstate dot edu> <52FB0686 dot 8080403 at gmail dot com> <52FB13E2 dot 1070107 at appstate dot edu> <724410821 dot 20140212111451 at mtu-net dot ru> <CAMCbSMoqb_TsY3BQSU-AwnCOuCYecwCw4YexBQuUhbAbpSNDQg at mail dot gmail dot com> <52FB8E3C dot 3030704 at appstate dot edu>
Scott T. Marshall writes:
> The strange thing is that gfortran does compile the
> code, but once compiled, the executables have strange behavior mainly
> involving problems reading in data files.
To me this rather indicates a bug in the code, probably involving bad
assumptions about what can be be done to files and in which order. For
starters you might check if the files are opened in binary mode.
> So it is not clear to me
> exactly what needs to be updated in the code.
Big can of worms. I've seen old Fortran code break on seemingly unrelated
things like a C library security update, not to say what happened when I
first tried to run it on an Alpha. You might try if the program
works correctly if compiled unoptimized. Another option is to
purposefully use a compiler that does things in a very different way and
see where it complains and/or breaks (I've been keeping f2c for that).
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptation for Waldorf microQ V2.22R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
--
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