public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "fxcoudert at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libfortran/22423] Warnings when building libgfortran Date: Thu, 18 Jan 2007 17:45:00 -0000 [thread overview] Message-ID: <20070118174534.30373.qmail@sourceware.org> (raw) In-Reply-To: <bug-22423-10258@http.gcc.gnu.org/bugzilla/> ------- Comment #9 from fxcoudert at gcc dot gnu dot org 2007-01-18 17:45 ------- Once that last warning is fixed, I'd really like libgfortran to be built with -Werror by default, at least on linux systems (it's known to issue tons of warnings on some non-C99 systems, so we can't make it the default unconditionaly). -- fxcoudert at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|unassigned at gcc dot gnu |fxcoudert at gcc dot gnu dot |dot org |org Status|NEW |ASSIGNED Last reconfirmed|2006-10-01 07:43:53 |2007-01-18 17:45:32 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22423
next prev parent reply other threads:[~2007-01-18 17:45 UTC|newest] Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-22423-10258@http.gcc.gnu.org/bugzilla/> 2005-10-02 18:01 ` pinskia at gcc dot gnu dot org 2006-05-19 17:04 ` fxcoudert at gcc dot gnu dot org 2006-05-19 17:05 ` fxcoudert at gcc dot gnu dot org 2006-05-20 2:56 ` jvdelisle at gcc dot gnu dot org 2006-05-20 3:30 ` jvdelisle at gcc dot gnu dot org 2006-10-01 7:44 ` fxcoudert at gcc dot gnu dot org 2006-10-01 16:38 ` howarth at nitro dot med dot uc dot edu 2007-01-18 17:45 ` fxcoudert at gcc dot gnu dot org [this message] 2007-01-18 19:18 ` howarth at nitro dot med dot uc dot edu 2007-01-18 19:32 ` fxcoudert at gcc dot gnu dot org 2007-03-04 8:32 ` fxcoudert at gcc dot gnu dot org 2007-10-07 21:48 ` tobi at gcc dot gnu dot org 2007-10-18 13:22 ` fxcoudert at gcc dot gnu dot org 2007-12-27 15:00 ` tkoenig at gcc dot gnu dot org 2009-05-03 16:29 ` fxcoudert at gcc dot gnu dot org 2009-05-03 19:29 ` jvdelisle at gcc dot gnu dot org 2009-05-07 21:42 ` fxcoudert at gcc dot gnu dot org 2009-05-07 22:03 ` fxcoudert at gcc dot gnu dot org 2009-05-27 1:23 ` jvdelisle at gcc dot gnu dot org 2009-06-14 9:06 ` fxcoudert at gcc dot gnu dot org 2009-07-05 9:24 ` fxcoudert at gcc dot gnu dot org 2009-07-05 9:24 ` fxcoudert at gcc dot gnu dot org 2009-07-13 6:27 ` burnus at gcc dot gnu dot org 2009-07-13 6:32 ` burnus at gcc dot gnu dot org 2005-07-12 3:27 [Bug libfortran/22423] New: " fengwang at gcc dot gnu dot org 2005-09-24 13:14 ` [Bug libfortran/22423] " fxcoudert 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=20070118174534.30373.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).