Bug#544844: doesn't use policy-mandated CFLAGS

2011-05-14 Thread Goswin von Brederlow
Package: debhelper Version: 8.1.2 Severity: normal File: /usr/bin/dh Hi, I just stumbled on the same issue. So what is the status of this now for debhelper? Will you add code in dh to automatically initialize the variables with dpkg-buildflags if they are unset? I don't believe this needs a new

Bug#544844: doesn't use policy-mandated CFLAGS

2010-05-28 Thread Raphael Hertzog
Hi, On Wed, 12 May 2010, Joey Hess wrote: > I'm not sure how all this ties in with the new dpkg-buildflags command. > The right thing might be for debhelper to use dpkg-buildflags to get > default (and configurable) values. > > * Introduce a new script called dpkg-buildflags: its purpose is to

Bug#544844: doesn't use policy-mandated CFLAGS

2010-05-12 Thread Joey Hess
Marcelo E. Magallón wrote: >  Since I didn't find any support for it, I went ahead and wrote a >  proof-of-concept patch (attached).  Examining a small sample of >  source packages indicates that this idiom is currently in use: > >  override_dh_auto_configure: >        dh_auto_configure -- CFLAGS=

Bug#544844: doesn't use policy-mandated CFLAGS

2010-02-20 Thread Marcelo E . Magallón
Hi,  For unrelated reasons I was looking at the example files  provided by debhelper and I noticed  /usr/share/doc/debhelper/examples/rules.tiny.  My first hunch  was that debhelper incorporates: 4.9.1. `debian/rules' and `DEB_BUILD_OPTIONS' -     Supp