|
Bugzilla – Full Text Bug Listing |
| Summary: | Qt headers throw dozens of compiler warnings | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Stefan Hundhammer <shundhammer> |
| Component: | KDE | Assignee: | E-mail List <kde-maintainers> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Major | ||
| Priority: | P5 - None | CC: | aj, kkaempf, matz, rguenther |
| Version: | RC 4 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Development | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | Patch for affected Qt headers | ||
|
Description
Stefan Hundhammer
2005-09-28 12:38:08 UTC
then disable that warning. See for example how KDE does it. (-Wno-non-virtual-dtor) fixing those warnings is binary incompatible. Are you kidding? Disabling warnings cannot be the way to go. And remember, this will not only suppress the warnings from those Qt headers, it will also suppress the same problem occurring in the applications. We have a zero warnings policy here. And we are really serious about that. I fully agree with Stefan here (and went through this for all my packages :-() but "fixing those warnings is binary incompatible" is indeed a problem. Aj, your call ... Maybe there is a way to tell gcc to disable this warning only for the affected headers - some "#pragma dontknowwhat". But disabling them general is really a bad approach IMHO. Compiler team, please provide some input here. To hack around this problem place #pragma GCC system_header at the top of the Qt include files triggering this warning. ***HACK ALERT!!!*** Thanks for that hint! Will attach patch that suppresses those warnings for the affected include files. Created attachment 51159 [details]
Patch for affected Qt headers
that patch doesn't solve the issue. anyway, closing. |