------- Comment #3 from rob1weld at aol dot com 2009-02-22 12:51 ------- (In reply to comment #1) > Rob, did you ever read http://gcc.gnu.org/bugs.html#report ? > > To be honest, I don't even know _what_ are you reporting here. There is no > point to post hundreds of lines from build logs, since this is too much for > anybody to even read it. Sorry. > > So, please stop wasting yours and others time and please post a precise > bugreport that _explains_ what you think is going wrong. On one or max two > screens of text, please. > > From the bug report guide, you will note following bullet: > > "Bugs in releases or snapshots of GCC not issued by the GNU Project. Report > them to whoever provided you with the release" > > FYI, "miro" (or whatever) is not issued by the GNU project. >
http://gcc.gnu.org/wiki/MIRO svn co svn://gcc.gnu.org/svn/gcc/branches/miro miro Who issues it ? > please post a precise bugreport that _explains_ what you think ... Read the title, it is a Werror. In addition to the Werror, while someone is doing that they may (or may not) desire to catch the few warnings in other files that are generating thousands of warnings (and lead to the Werror). Two ways to fix this, a simple exclusion or fix all the warnings. > To be honest, I don't even know _what_ are you reporting ... This much we know. We thank you for your input on something that you know nothing about, do you have more to offer? Did you ever read: http://gcc.gnu.org/svn.html#devbranches The "miro branch" is listed under "Active Development Branches". Lets go with this Branch needs it's web page fixed (instead of exchanges of rudeness). Rob -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39262
