public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "anlauf at gmx dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/55534] New: -Wno-missing-include-dirs does not work with gfortran Date: Thu, 29 Nov 2012 20:31:00 -0000 [thread overview] Message-ID: <bug-55534-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55534 Bug #: 55534 Summary: -Wno-missing-include-dirs does not work with gfortran Classification: Unclassified Product: gcc Version: 4.8.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned@gcc.gnu.org ReportedBy: anlauf@gmx.de Hi, a non-existent include directory generates a warning. Unfortunate it cannot be suppressed by -Wno-missing-include-dirs: % gfc-trunk -I/no/such/dir -Wno-missing-include-dirs xxx.f90 Warning: Nonexistent include directory "/no/such/dir" f951: warning: command line option '-Wno-missing-include-dirs' is valid for C/C++/ObjC/ObjC++ but not for Fortran [enabled by default] It would be nice if this worked with Fortran.
next reply other threads:[~2012-11-29 20:31 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-11-29 20:31 anlauf at gmx dot de [this message] 2012-11-29 20:32 ` [Bug fortran/55534] " anlauf at gmx dot de 2012-12-04 23:02 ` anlauf at gmx dot de 2012-12-05 9:29 ` burnus at gcc dot gnu.org 2012-12-05 21:44 ` anlauf at gmx dot de 2012-12-06 0:04 ` burnus at gcc dot gnu.org 2012-12-07 21:10 ` anlauf at gmx dot de 2012-12-13 21:11 ` anlauf at gmx dot de 2014-09-09 21:39 ` manu at gcc dot gnu.org 2014-12-29 20:00 ` anlauf at gmx dot de 2014-12-29 21:28 ` manu at gcc dot gnu.org 2021-09-17 9:42 ` burnus at gcc dot gnu.org 2021-09-17 13:02 ` burnus at gcc dot gnu.org 2021-09-21 6:28 ` cvs-commit at gcc dot gnu.org 2021-09-21 7:13 ` burnus at gcc dot gnu.org 2021-09-22 18:58 ` cvs-commit at gcc dot gnu.org 2021-09-24 7:31 ` cvs-commit at gcc dot gnu.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=bug-55534-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).