* Ilya B <email address hidden> [2009-06-18 13:09:16 CEST]:
> I contacted upstream about the warnings in network.cpp, and they say
> that it's not a bug in Wesnoth (and that we should probably ignore the
> warning rather than turn off optimization... well, maybe).
> http://gna.org/bugs/?13711
Erm ... Did you read the bug log? I commented on exactly this already
and it got acknowledged by gcc people even. Let me quote for your
pleasure again:
,-------------------------------> quote <-------------------------------
| That's a known bug in gcc 4.4. Either get it explicitly to use gcc 4.3
| or make it use gcc 4.5 in which this bug got fixed again. See also these
| reports about it:
| <http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=528587>
| <http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40156>
`-------------------------------> quote <-------------------------------
No need to bring up an issue that everyone agreed upon already. :)
* Ilya B <email address hidden> [2009-06-18 13:09:16 CEST]: gna.org/ bugs/?13711
> I contacted upstream about the warnings in network.cpp, and they say
> that it's not a bug in Wesnoth (and that we should probably ignore the
> warning rather than turn off optimization... well, maybe).
> http://
Erm ... Did you read the bug log? I commented on exactly this already
and it got acknowledged by gcc people even. Let me quote for your
pleasure again:
,------ ------- ------- ------- ----> quote <------ ------- ------- ------- ---- bugs.debian. org/cgi- bin/bugreport. cgi?bug= 528587> gcc.gnu. org/bugzilla/ show_bug. cgi?id= 40156> ------- ------- ------- ----> quote <------ ------- ------- ------- ----
| That's a known bug in gcc 4.4. Either get it explicitly to use gcc 4.3
| or make it use gcc 4.5 in which this bug got fixed again. See also these
| reports about it:
| <http://
| <http://
`------
No need to bring up an issue that everyone agreed upon already. :)
... *puzzled*
Rhonda