This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c/31105] build broken (trunk rev 122742)
- From: "mtrudel at gmx dot ch" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 9 Mar 2007 14:12:32 -0000
- Subject: [Bug c/31105] build broken (trunk rev 122742)
- References: <bug-31105-13027@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #2 from mtrudel at gmx dot ch 2007-03-09 14:12 -------
Thanks. But actually I also tried to start a discussion why such compilation
errors can happen:
This strongly remembers me to http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30510
Is it possible that some flags trigger the "warnings being treated as errors"
but most developers don't use this? That would explain why people stumble over
it while compilation seems to work for the developers?!
Of course I could be completely wrong. But if I'm right, there would be an easy
way to prevent such build breaks...
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31105