GNOME Bugzilla – Bug 577264
Building glib-2.18.4-r1 on Gentoo fails with "poor code kills airplanes"
Last modified: 2011-10-25 02:17:35 UTC
Please describe the problem: Emerging glib fails with the following messages: * QA Notice: Package has poor programming practices which may compile * fine but exhibit random runtime failures. * gobject.c:2082: warning: dereferencing type-punned pointer will break strict-aliasing rules * gobject.c:2088: warning: dereferencing type-punned pointer will break strict-aliasing rules * gobject.c:2346: warning: dereferencing type-punned pointer will break strict-aliasing rules * gobject.c:2383: warning: dereferencing type-punned pointer will break strict-aliasing rules * gobject.c:2400: warning: dereferencing type-punned pointer will break strict-aliasing rules * gparam.c:252: warning: dereferencing type-punned pointer will break strict-aliasing rules * Please do not file a Gentoo bug and instead report the above QA * issues directly to the upstream developers of this software. * Homepage: http://www.gtk.org/ * * ERROR: dev-libs/glib-2.18.4-r1 failed. * Call stack: * misc-functions.sh, line 717: Called install_qa_check * misc-functions.sh, line 418: Called die * The specific snippet of code: * [[ ${abort} == "yes" ]] && hasq stricter ${FEATURES} && die "poor code kills airplanes" * The die message: * poor code kills airplanes Steps to reproduce: emerge glib (2.18.4-r1) on Gentoo Actual results: See problem description above Expected results: A proper installation. Does this happen every time? Yes Other information: Gentoo 2008.0 on AMD64
This still does not tell where exactly the issue is. If Gentoo has strict compile flags that treat warnings as errors, okay. If Gentoo wants to be funny by providing useless error messages: Please file a bug against Gentoo. :-)
"blocker"?
Dev profiles (not intended for end users) on gentoo fail on certain warnings that tend to cause run-time failures. I'm not sure why this user was seeing this, unless he mistakenly used a dev profile.
According to https://bugs.gentoo.org/show_bug.cgi?id=264686 this should be fixed since SVN rev 7875.