public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "axel.ehrich@tu-clausthal.de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/114922] New: fsyntax-only need the modules Date: Thu, 02 May 2024 12:47:08 +0000 [thread overview] Message-ID: <bug-114922-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114922 Bug ID: 114922 Summary: fsyntax-only need the modules Product: gcc Version: 13.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: axel.ehrich@tu-clausthal.de Target Milestone: --- Created attachment 58087 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=58087&action=edit Short Example for this problem I encounter the following problem with gfortran: When I try to compile a file (such as the one attached) with the options -c -fsyntax-only, that is "gfortran -c -fsyntax-only syntax-only_test.f90" I receive the following error message: ------------------------------------------------------ syntax-only_test.f90:2:5: 2 | use module | 1 Fatal Error: Cannot open module file 'module.mod' for reading at (1): No such file or directory compilation terminated. ----------------------------------------------- One purpose of the option "-fsyntax-only" is to create the module files (.mod), however, without doing the compilation that would require module files. The observed behaviour appears like a bug in gfortran. I used https://aoterodelaroza.github.io/devnotes/modern-fortran-makefiles/ to look how i can solve the problem with the depends of mod files. Best regards, Axel
next reply other threads:[~2024-05-02 12:47 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-05-02 12:47 axel.ehrich@tu-clausthal.de [this message] 2024-05-02 16:43 ` [Bug fortran/114922] " anlauf at gcc dot gnu.org 2024-05-02 17:38 ` kargls at comcast dot net 2024-05-03 10:50 ` axel.ehrich@tu-clausthal.de 2024-05-03 13:38 ` mikael at gcc dot gnu.org 2024-05-06 5:58 ` axel.ehrich@tu-clausthal.de
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=bug-114922-4@http.gcc.gnu.org/bugzilla/ \ --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).