| Summary: | DBUS-PYTHON blocker warnings | ||
|---|---|---|---|
| Product: | dbus | Reporter: | Eduardo Silva <edsiper> |
| Component: | python | Assignee: | John (J5) Palmieri <johnp> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | blocker | ||
| Priority: | highest | ||
| Version: | unspecified | ||
| Hardware: | Other | ||
| OS: | Linux (All) | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
|
Description
Eduardo Silva
2007-01-24 11:48:47 UTC
These warnings are not a problem, which is why configure.ac tries to disable them by using -Wno-missing-field-initializers; this is how you do multiple-version compatibility in CPython, which has class structures that increase in size every few versions. The CPython API/ABI is such that leaving the end of the structure implicitly zero-initialized is always safe. What gcc version are you using, and does it support the -Wno-missing-field-initializers option? We might have to do something like not using -Wextra unless -Wno-missing-field-initializers also works. In a release tarball warnings aren't fatal in any case, -Werror is only enabled for the git tree. Could Werror be enabled only for maintainer mode or something... This is going to screw us pretty badly. Changed in git as requested. (Doesn't need to go into a release to be relevant, since -Werror only happens in non-release builds) |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.