public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dannysmith at users dot sourceforge dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/25502] Werror problem in build Date: Sun, 04 Jun 2006 11:02:00 -0000 [thread overview] Message-ID: <20060604110234.29590.qmail@sourceware.org> (raw) In-Reply-To: <bug-25502-10259@http.gcc.gnu.org/bugzilla/> ------- Comment #7 from dannysmith at users dot sourceforge dot net 2006-06-04 11:02 ------- In my local tree (and in the 3.4.x mingw tree), I have added a modification and extension of this patch: http://gcc.gnu.org/ml/gcc-patches/2004-11/msg02296.html I plan to follow up in stage 1 of 4.3 This patch silences the worst of the warnings. However, because of the -pedantic switch, I still get warnings like ../../gcc/gcc/gcov-dump.c:408: warning: ISO C does not support the 'I64' printf length modifier -Wno-pedantic-errors doesn't work for me, so --disable-werror is still necessary. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25502
next prev parent reply other threads:[~2006-06-04 11:02 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-12-20 11:30 [Bug bootstrap/25502] New: " fxcoudert at gcc dot gnu dot org 2005-12-20 11:35 ` [Bug bootstrap/25502] " fxcoudert at gcc dot gnu dot org 2005-12-20 16:37 ` pinskia at gcc dot gnu dot org 2005-12-20 16:44 ` mmitchel at gcc dot gnu dot org 2005-12-22 7:35 ` fxcoudert at gcc dot gnu dot org 2005-12-22 8:19 ` mark at codesourcery dot com 2005-12-23 5:44 ` pinskia at gcc dot gnu dot org 2006-06-04 9:47 ` rmathew at gcc dot gnu dot org 2006-06-04 11:02 ` dannysmith at users dot sourceforge dot net [this message] 2007-05-22 12:06 ` fxcoudert at gcc dot gnu dot org 2007-07-17 21:13 ` pinskia at gcc dot gnu dot org 2008-03-19 6:43 ` zuxy dot meng at gmail dot com 2008-03-19 7:10 ` pinskia at gcc dot gnu dot org 2008-03-19 21:36 ` dannysmith at users dot sourceforge dot net 2008-05-11 3:05 ` aaronavay62 at aaronwl dot com 2008-05-11 4:49 ` [Bug bootstrap/25502] I64d format " aaronavay62 at aaronwl dot com 2008-05-11 12:16 ` joseph at codesourcery dot com 2008-05-11 12:18 ` joseph at codesourcery dot com 2008-05-11 21:25 ` aaronavay62 at aaronwl dot com 2008-05-19 10:28 ` ktietz at gcc dot gnu dot org 2008-08-24 1:18 ` aaronavay62 at aaronwl dot com 2008-09-14 3:28 ` aaronavay62 at aaronwl dot com 2008-10-13 10:41 ` ktietz 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=20060604110234.29590.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).