From: Mark Hadfield <mark.hadf@gmail.com>
To: Cygwin <cygwin@cygwin.com>
Subject: Re: Incorrect module file format in Fortran netCDF package
Date: Wed, 21 Jan 2015 04:40:00 -0000 [thread overview]
Message-ID: <CALLo=nonn0EexoNONUY44mbkWn1M9=E4mVhgbPRdohjup0edjg@mail.gmail.com> (raw)
Following up my previous message, this from
https://gcc.gnu.org/wiki/GFortran/News#gfortran_4.9.1 indicates that
the problem is due to the GCC upgrade from 4.8 to 4.9:
Module files: The version of the module files (.mod) has been
incremented; additionally, module files are now compressed. Fortran
MODULEs compiled by earlier GCC versions have to be recompiled, when
they are USEd by files compiled with GCC 4.9, because GCC 4.9 is not
able to read .mod file of earlier GCC versions; attempting to do so
gives an error message. Note: The ABI of the produced assembler data
itself has not changed: object files and libraries are fully
compatible to older versions. (Except for the next items.)
--
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
next reply other threads:[~2015-01-21 3:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-21 4:40 Mark Hadfield [this message]
2015-01-21 9:02 ` Marco Atzeri
-- strict thread matches above, loose matches on Subject: below --
2016-02-29 22:40 Mark Hadfield
2016-03-01 5:35 ` Marco Atzeri
2015-01-20 23:50 Mark Hadfield
2013-10-04 4:11 Mark Hadfield
2013-10-04 4:32 ` Mark Hadfield
2013-10-04 8:57 ` marco atzeri
2013-10-04 9:57 ` marco atzeri
2013-10-06 21:50 ` Mark Hadfield
[not found] ` <A4BDD8E3859F92478F09D5AACD6D79C0956EF4DC@welwexmb01.niwa.local>
2013-10-07 1:46 ` marco atzeri
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='CALLo=nonn0EexoNONUY44mbkWn1M9=E4mVhgbPRdohjup0edjg@mail.gmail.com' \
--to=mark.hadf@gmail.com \
--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).