On Sat, Apr 14, 2012 at 02:42:50PM -0400, Joey Hess wrote: > This same thing was recently done for perl. (#662666) > > To make changes to build flags used in v9, there needs to be a proof > that it doesn't break anything (or work done to identify what does break, > and fix it).
Hello, At the moment there are 573 packages which build-depend on cmake. 74 of those use compat=9. 9 of the compat=9 packages already have a fix to pass CPPFLAGS to CFLAGS so the change won't affect them (double CPPFLAGS are not a problem). The following 65 packages are not using CPPFLAGS yet: - alure - amarok - apiextractor - bibletime - bluedevil - charls - chromaprint - cminpack - cutesdr - debconf-kde - eigen3 - exodusii - fcitx - fluidsynth - generatorrunner - gnome-pie - gtk2-engines-oxygen - holdingnuts - jthread - k3d - k9copy - knemo - korundum - ktorrent - kvirc - kvpm - libbluedevil - libdrumstick - libechonest - libical - libindicate-qt - libktorrent - lightspark - mini18n - mriconvert - musescore - ogre - otcl - pdf-presenter-console - plasma-widget-message-indicator - plasma-widget-yawp - pyside-mobility - qapt - qjson - qtoctave - qtruby - rekonq - remmina - shiboken - sikuli - skanlite - slim - smokegen - smokekde - smokeqt - swami - taglib - tclcl - tellico - tulip - uhd - ulatencyd - vtk - xdmf - yabause I've rebuild all of them with the patched debhelper and all (except one, see below) build fine. Build logs are available at [1]. alure (1.2-4) FTBS before and after the CPPFLAGS change and is not affected by it (something is wrong in debian/control). I hope that's enough to get this change into v9. > If that's not practical, this would need to be deferred to v10. Regards, Simon [1]: http://ruderich.org/simon/debhelper-cppflags/ -- + privacy is necessary + using gnupg http://gnupg.org + public key id: 0x92FEFDB7E44C32F9
pgpHDxbm9HlGW.pgp
Description: PGP signature
