Package: dpkg-dev Version: 1.14.29 dpkg-dev nowadays sets various *FLAGS variables in the environment. However some upstream build systems (eg, the one in xen-unstable.hg) break if these variables are set eg because they do stuff like LDFLAGS ?= -Lsomething_we_really need
Arguably those upstream build systems are broken, but the Debian packaging system needs to be able to encapsulate broken build systems as well as non-broken ones. Currently the only way to fix this is to write, in debian/rules, something like this: unexport LDFLAGS unexport CPPFLAGS unexport CXXFLAGS unexport MFLAGS unexport CFLAGS unexport FFLAGS However, there is no way to get a complete list of these flags variables, future versions of dpkg-dev may set more of them, and all of this is not at all under the control of the package maintainer. Something better should be done. I don't think that packages' debian/rules files are required by policy to work properly if LDFLAGS etc. are set in the environment. I think dpkg-buildpackage should set _only_ DEBIAN_*FLAGS and expect debian/rules to honour them. Ian. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
