See gcc commands in the build log, and note that -debuginfo contains no sources. This looks like a regression, 0.8.4-4 seems to have been built with $RPM_OPT_FLAGS. http://kojipkgs.fedoraproject.org/packages/compizconfig-backend-gconf/0.8.4/4.fc14/data/logs/x86_64/build.log http://kojipkgs.fedoraproject.org/packages/compizconfig-backend-gconf/0.9.2.2/0.1.git86d949fad4.fc15/data/logs/x86_64/build.log
hum, some of the commands get them, some don't...I'll look into it. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
This bug has been triaged
so, it turns out this is wider - actually compiz itself builds without cflags, and the same for all compiz stuff that uses cmake. it was due to a bug in a cmake file that compiz itself and all dependent bits include, which set CMAKE_C_FLAGS without including $CMAKE_C_FLAGS to keep whatever flags were previously set, so it overrode any you passed in. I'm fixing this in compiz -11 and will then rebuild all the other packages, and they should then pick up the cflags correctly. I've sent the patch upstream to Sam. Thanks for the catch!
okay, this should be fixed now: I've rebuilt all compiz cmake bits (I think) and checked the cflags were correctly used. I also checked the debuginfo for backend-gconf is there. thanks again for the report.