>> I wonder if there is any sensible way for dpkg-buildflags to detect (or >> maybe just be told) which compile will be used for a build? Perhaps it >> could take a new argument that would allow it to select flags based on the >> compiler name and version? >> >> dpkg-buildflags --compiler=gcc-4.7 > > There are very legitimate reasons for using an older gcc version, and > breaking all the packages that do that is sort of unkind. > > Especially when some of them already export either CC=gcc-4.8 or > CXX=g++-4.8 in debian/rules (like chromium, oxref, and spek), which > would make it rather convenient to detect the compiler in use. Other > packages in that set don't do that but patches could be proposed for > those packages so they don't have this problem in the future.
Here is the complete set of packages in that list that do export CC/CXX: chromium contextfree flexc++ gpg-remailer llvm-toolchain-snapshot openimageio oxref spek And here are the three that don't, but than can be fixed fairly easily: ccbuild higan webkitgtk So 8 out of 11 already export sufficient information, which is a pretty good ratio. Best wishes, Mike -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: https://lists.debian.org/CANTw=mp3tfgvcyzvcv60p_saa3ezhrlg8jbklscbyspy0cx...@mail.gmail.com
