Hi,
In particular the environment variables to set are generated by
"dpkg-architecture -s" and "dpkg-buildflags --export", so you might
run those commands to see exactly what dpkg-buildpackage was injecting
into your environment.
However, as previously noted, from dpkg-dev 1.16.1 (uploaded last
week) the bit from dpkg-buildflags will no longer be automatically
exported into the build environment. So you will need to adjust
debian/rules anyway to pick those up.
...Milligan
On Mon, 26 Sep 2011, Michael Banck wrote:
> > will fail with a weird compile error somewhere in the middle of the
> > build process. It appears as if dpkg-buildpackage after all is not
> > simply the sequence of commands that the man-page will make us
> > believe?
> One issue you could run to is that dpkg-buildpackage (at least the
> version in squeeze, the latest upload has reverted this) exports a set
> of CFLAGS etc.
> If your software overloads CFLAGS for required flags or just doesn't
> compile with the default CFLAGS ("-g -O2 -Wall" I believe), this could
> be the problem.
--
Attachment:
signature.asc
Description: Digital signature