Re: Mass GCC 4.6 bug filling (Re: Bug#624997: writerperfect: FTBFS: Style.hxx:36:45: error: 'NULL' was not declared in this scope)
On 05/04/2011 12:24 AM, Cyril Brulebois wrote:
(not a gcc maintainer)
Charles Plessy<firstname.lastname@example.org> (04/05/2011):
I just got a bug from you explaining some changes (= more FTBFS)
about 4.6.1. Will there be similar 4.6.x changes in the future ?
my reading of it is that to prevent too many FTBFSes while introducing
4.6 in Debian, some changes were delayed (“reverted through Debian
patches”) until 4.6.1 is released and uploaded.
Assuming you're talking about -Wunused-*, those are mentioned on the
upstream upgrading / porting page:
| New -Wunused-but-set-variable and -Wunused-but-set-parameter warnings
| were added for C, C++, Objective-C and Objective-C++. These warnings
| diagnose variables respective parameters which are only set in the
| code and never otherwise used. Usually such variables are useless and
| often even the value assigned to them is computed needlessly,
| sometimes expensively. The -Wunused-but-set-variable warning is
| enabled by default by -Wall flag and -Wunused-but-set-parameter by
| -Wall -Wextra flags.
I don't think more changes are planned for the 4.6.x series; you'll
have to wait for 4.7 to get more changes.
yes, thanks for the clarification. bugs for these kind of errors are now filed,
see , although I was a bit sloppy scanning the build logs, so there are some