public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/38248] Fatal Error: Reading module mmm: Expected left parenthesis Date: Mon, 24 Nov 2008 16:21:00 -0000 [thread overview] Message-ID: <20081124162018.28899.qmail@sourceware.org> (raw) In-Reply-To: <bug-38248-12292@http.gcc.gnu.org/bugzilla/> ------- Comment #2 from burnus at gcc dot gnu dot org 2008-11-24 16:20 ------- The error message looks as if you are mixing a gfortran 4.3 compiled .mod file with a gfortran 4.4 compiler (or vice versa). While the gfortran 4.3 compiled *.o/*.so/*.a files are supposed to be compatible with 4.4's libgfortran.so, for .mod files this is not the case. (.mod files are not like *.h files compiler independent, but simply a "binary" dump of the interfaces of a single module.) I think a solution would be to create a version number for the .mod data and add a checking. -- burnus at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |burnus at gcc dot gnu dot | |org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38248
next prev parent reply other threads:[~2008-11-24 16:21 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-11-24 15:20 [Bug fortran/38248] New: " jan dot kratochvil at redhat dot com 2008-11-24 15:38 ` [Bug fortran/38248] " mikael at gcc dot gnu dot org 2008-11-24 16:21 ` burnus at gcc dot gnu dot org [this message] 2008-11-24 16:36 ` [Bug fortran/38248] Ignored temporary module files manipulation errors jan dot kratochvil at redhat dot com 2008-11-24 16:41 ` jan dot kratochvil at redhat dot com 2008-11-25 12:54 ` burnus at gcc dot gnu dot org 2008-12-08 23:05 ` mikael at gcc dot gnu dot org 2008-12-09 21:40 ` dfranke at gcc dot gnu dot org
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=20081124162018.28899.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /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: linkBe 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).